Configuring InspIRCd and Anope

From the makers of InspIRCd.

Contents 1 InspIRCd and Anope 1.1 InspIRCd Modules Required 1.2 InspIRCd Modules Suggested 1.3 Anope Configuration 1.4 InspIRCd Configuration 2 Examples 2.1 Link Block 2.2 Alias Block

InspIRCd and Anope

There doesn't seem to be a guide for Anope & InspIRCd...so here ya go ;-)

This was written for InspIRCd-1.1.19+Cheshire(r0) and Anope v1.7.21

InspIRCd Modules Required

• Modules/spanningtree - Required for linking with anything
• Modules/globops - Required for Anope
• Modules/services - NOT the m_services_account module! That account one doesn't work with Anope.

InspIRCd Modules Suggested

• Modules/alias - Not required, but very useful for creating aliases: /nickserv and /ns (as well as for the other services bots)
• Modules/svshold - Only required if you enable the option "UseSVSHOLD" in Anope (Which is recommended)

Anope Configuration

• Use the inspircd11 ircd module: IRCDModule "inspircd11"
• You should enable the UseSVSHOLD option (Not required, but definitely recommended). NOT SVS2MODE!
• Comment out the "Numeric" option, as it is not needed
• Comment out the "UseTokens" option, as InspIRCd does not support TOKEN commands.

All other settings are user preference :D

InspIRCd Configuration

• See the below examples for the <link> block
• Make sure you set the <uline> block to the same hostname as in the "ServerName" in the anope config.
• See the below examples for an <alias> block that works with Anope

And that's pretty much it! See some examples below for more info.

Examples

Link Block

• Note, that "sendpass" inside the <link> block can be absolutely anything, it doesn't matter. sendpass is used for InspIRCd connecting OUT TO the server, which never happens with services. Services connect INTO the IRCd.

Anope Link Block:

RemoteServer    127.0.0.1       7002    "insert_password_here"

InspIRCd Link Block:

<link   name="services.domain.tld"
        ipaddr="localhost"
        port="7002"
        allowmask="127.0.0.1"
        sendpass="must_be_something_other_than_null_or_the_link_block_will_be_ignored"
        recvpass="insert_password_here">

<uline server="services.domain.tld" silent="no">

Alias Block

• The following set of aliases will give you the following commands: /nickserv, /chanserv, /hostserv, /botserv, /operserv, /ns, /cs, /hs, /bs, and /os.

# This first alias fixes a glitch in xchat 2.6.x and above and the way it
# assumes IDENTIFY must be prefixed by a colon (:) character. It should
# be placed ABOVE the default NICKSERV alias (the first example) listed
# above.
<alias text="NICKSERV" format=":IDENTIFY *" replace="PRIVMSG NickServ :IDENTIFY $3-" requires="NickServ" uline="yes">
<alias text="NICKSERV" replace="PRIVMSG NickServ :$2-" requires="NickServ" uline="yes">
<alias text="CHANSERV" replace="PRIVMSG ChanServ :$2-" requires="ChanServ" uline="yes">
<alias text="HOSTSERV" replace="PRIVMSG HostServ :$2-" requires="HostServ" uline="yes">
<alias text="BOTSERV" replace="PRIVMSG BotServ :$2-" requires="BotServ" uline="yes">
<alias text="OPERSERV" replace="PRIVMSG OperServ :$2-" requires="OperServ" uline="yes" operonly="yes">
<alias text="NS" replace="PRIVMSG NickServ :$2-" requires="NickServ" uline="yes">
<alias text="CS" replace="PRIVMSG ChanServ :$2-" requires="ChanServ" uline="yes">
<alias text="HS" replace="PRIVMSG HostServ :$2-" requires="HostServ" uline="yes">
<alias text="BS" replace="PRIVMSG BotServ :$2-" requires="BotServ" uline="yes">
<alias text="OS" replace="PRIVMSG OperServ :$2-" requires="OperServ" uline="yes" operonly="yes">

• Alternatively, if you do not wish to have this mass of text in your configuration, you can use the <include> tag to include one of the distributed alias configuration files.

<include file="aliases/anope.conf">

This is just an example, as we are discussing Anope configuration. Any configuraion file, whether distributed with InspIRCd or created by you, can be used.