[ILUG] a closed irc server

[Colm Buckley]

On Wed 20 Feb 2002 12:58, kevin lyda wrote:

> ok, nifty.  now does anyone have experience in convincing two ircd
> 2.10.3p3 servers to talk to each other.  i get very little feedback from
> the servers:

Yep.

The Undernet ircd allows a "star" topology; of which 2 servers is of
course a degenerate case:

On server1's ircd.conf:

M:server1.domain.net:*:My Main IRC server:8005:22
C:server2.domain.net:plaintextpassword1:server2.domain.net:8005:90
N:server2.domain.net:encryptedpassword2:server2.domain.net::90
P:*:*:*:6667

The M: line tells the server that it'll be accepting connections on
port 8005 (this is commonly used for server to server connections).
The last number in the line is the server identifier; should be an
integer, different for each server in the network.

The C: line tells it to attempt to connect to server2 on port 8005
using the specified plaintext password (connection class 90).

The N: line tells it to allow connections from server2 using the
specified password (encrypted using "mkpasswd" if your ircd is
compiled with encryption).

The P: line tells it to allow non-server connections on port 6667.

On server2's ircd.conf:

M:server2.domain.net:*:My Main IRC server:8005:23
C:server1.domain.net:plaintextpassword2:server1.domain.net:8005:90
N:server1.domain.net:encryptedpassword1:server1.domain.net::90
P:*:*:*:6667

Note that the C: line here contains the plaintext version of the
password which appears encrypted in server1's N: line, and vice versa.

Hope this helps,

          Colm

-- 
Colm Buckley : Systems Architect at NewWorldIQ
Personal : colm at tuatha.org | +353 87 2469146 | www.colm.buckley.name
Business : colm at newworldiq.com | +353 1 4334334 | www.newworldiq.com
Those who live by the sword get shot by those who don't.