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

[jv@xxxxxxxxxx (Jakub Vlasek)]

On Thu, Dec 13, 2001 at 11:58:02PM +0100, Tristan Nowak wrote:
> Greetings to all Linux Professionals,
> 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). After connecting, however,
> everything works fine. I have found some indication on the web that the DNS
> lookup may be the problem (as I dont have a DNS installed on my system). But
> when I set the /etc/resolv.conf and nsswitch.conf not to look for any DNS and start the
> server with the -s option (which should prevent iauth to start) it still doesn't
Iauth has nothing to do with dns timeout (yet), we are planning to add
define/option to turn off the resolver completely in future versions of ircd.

> work. Strangely enough it works when I connect to the internet and set a
> suitable nameserver. (But then I still have a connection accept time of 2
> seconds, which actually is to much). By the way I compiled with #undef

That might be because, as others mentioned, because of identd lookup if something is firewalled, OR it might be still dns problem - depends how remote
dns server is configured - resolving reserved adresses might take some time.
(ie 10.x, 192.168.x .. )

> SLOW_ACCEPT so that can't be the problem and I tried it with the undernet
> source, too, which also didn't work.

I guess best thing would be to setup local nameserver, and make it 
authoritative for your local reverse domain (like 168.192.in-addr.arpa), 
it doesn't need to be populated, but ircd will know that host doesn't have
any reverse immediately.

best regards
	JV
	
> 
> Any suggestions?
>