[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problems running self-compiled IRCD on my 486 DX 33 Debian Linux 2.0 Server (long connection accept time)



> -> Because I wanted a max. nickname length of 20 (not 9) I had to compile
> -> the ircd server source on my own. I took the latest version from
> -> ftp.irc.org/server. Compiling worked fine on my 486 Linux Server, but I
> -> have the problem that every connection attempt from another LAN PC
needs
> -> about 25 seconds to be accepted (which is way to long).
>
> When you connect the IRC server, it connects back to ports 113 to get
ident
> reply. If you have mod_socks configured in iauth, it also checks port 1080
> if there are no socks running on it. Also, I am not sure if dns lookups
> don't take some time and what's the dns tim eout in ircd.

The problem is more simple.
The server might be protected by a firewall or packet filter.
The latter allowing only connections to IRC port 6667.
So any scans outgoing from iauth may not get any answers back at all, not
even a RST.
TCP timeout is 30 seconds by default as far as I remember.
On the other side, some users may also have filtering protections which
turns out to the same result.

CHaiNeSS