Despite the mail fuckup, I felt I should answer this question :-) Peter, You don't specify which irc server you are connecting to, however, most irc networks do an IDENT lookup to try an keep clones to a minimum. ie, if you connect to the same server from the one IP address with the same IDENT it will kick you. Most efnet and DALnet servers will not allow you to connect at all without IDENT these days... now, mIRC has an ident server built in, however, if you are behind a firewall, obviously the irc server cannot connect back to you client. The problem being that you are running SuSEfirewall which will be "dropping" all packets to the IDENT port rather than sending an RST (reset) to say that the port is closed. Therefore the irc server is waiting up to the timeout limit for a reply to it's ident request. The simplest way to fix this is allow the ident port to you firewall, but not run the service. This way your firewall will respond correctly with an RST (ie. closed port, go away please) rather than making the IRC server wait. Ilternatively if you need ident you could consider running IDENT locally on the firewall, or use the IDENT pass through feature in the DANTE socks server that comes with SuSE 7.0. Note: I don't think the NEC reference implementation of socks supports this, so make sure u use dante. Hope that helps dude. Nix At 10:40 PM 9/11/2000 +0100, Peter ten Have wrote:
Hello,
Following Marc's advise not to use IP masq but proxy's I've installed Socks5 for serving mIRC and Napster on the clients. So far so good. After updating 6.3 on the gateway from a SuSE ftp mirror and SuSEfirewall from 2.4 to 3.0 (exactly the same config's), mIRC only connect to the IRC server AFTER sending the first ping. Socks5 reports a connection with the IRC server and traffic is accepted by the firewall.
Anyone knows what causes this delay?
BTW: Napster connects immediately
Thank you, Peter
--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com