Basically, listen * { ... }; will make the ircd bind to _all
available interfaces_ on the specified ports. So, if your server has
two network interfaces (i.e. 192.168.0.1 and 10.0.0.1) it will bind
to these, and (| think) 127.0.0.1 too.
It's possible that if for any reason any ports on an interface were
already used (i.e. 10.0.0.1 on port 6667), it would block the _whole_
listen config section. It's not a situation I considered testing.
It's generally a bad idea to use 'listen *' statements for a server.
I would recommend listening on a dedicated IP, or just the server/
systems IP address.
Philip: have you checked the server's error log to see if it has
reported anything wrong? (Assuming you have error logging enabled in
the server config file.)
Alasdair
On 30 Sep 2005, at 12:04, Marc Haber wrote:
On Fri, Sep 30, 2005 at 11:38:10AM +0100, Philip Craig wrote:
listen * {
range 6660-6669;
port 7000;
};
What does happen if you replace the "*" with your IP address, and
issue a single "port 6667;" statement? I know that this is not what
you intend to do, but it might enlighten us where to look for the
issue.
Greetings
Marc
--
----------------------------------------------------------------------
-------
Marc Haber | "I don't trust Computers. They | Mailadresse
im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621
72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 621
72739835
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
