[ILUG] IRCD problems

[Niall O Broin]

On Tue, Jul 17, 2001 at 05:22:16AM -0400, Wesley Darlington wrote:

> Is it possible that port 6667 is blocked by the colo?

Possible, but unlikely, and not, as it turned out, the case.

> If you have tcpserver[1], experiment with different ports...
>     tcpserver 0 6667 /bin/sh

Thank you Wesley - this put me on the track to the truth. I got a hold of
the tcpserver suite and I did 

tcpserver 0 6667 date

and could get the date with tcpclient from another box, so no problems as
such connecting to 6667. In the ircd configuration file is a line

M:some.where.com:*:A RedHat Linux IRC Server:6667

which tells the server to run on port 6667

and then a number of lines like

P:*:*:*:6669
P:*:*:*:6668
P:*:*:*:6666
P:*:*:*:6665
P:*:*:*:6664
P:*:*:*:6663
P:*:*:*:6662
P:*:*:*:6661
P:*:*:*:6660

which tell the server to also listen on those other ports in case a manic
client blocks 6667. This configuration file is more or less identical to the
one which does work (it was copied from there) but this is v. 2.10.3 whereas
the working one is 2.9.2. 

I then tried to connect to any of the ports specified in the P: lines and
they all worked, but 6667 did not. I then added a line like 

P:*:*:*:6667

and I was sucking diesel. I can only presume that there was a subtle
operational change between 2.9.2 and 2.10.3 which meant that the port
specified in the M:  line was NOT used by the server. I have the source for
2.10.3 and the changelog's last entry is 1991 so that's not a lot of help
and at this point I couldn't be arse looking through the source to see where
it parses the files and decides what ports to listen on. Problem solved, and
filed away for later forgetting :-)



Regards,




Niall