Date: Tue, 24 Aug 2004 16:15:32 +0300 From: Pavel Gulchouck <gul@gul.kiev.ua> To: Richard Wendland <richard@codeburst.co.uk> Cc: freebsd-net@freebsd.org Subject: Re: FIN_WAIT_2 timeout Message-ID: <20040824131532.GA20828@happy.kiev.ua> In-Reply-To: <200408241129.i7OBTg917650@starburst.demon.co.uk> References: <412B1883.9C3E38C2@freebsd.org> <200408241129.i7OBTg917650@starburst.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 24, 2004 at 12:29:42PM +0100, Richard Wendland writes: > >> http://httpd.apache.org/docs/misc/fin_wait_2.html says that FreeBSD > >> has a timeout for FIN_WAIT_2 state, but I don't see it. >> >> Very strange... RW> This is somewhat similar to a problem I explained a few months back: RW> http://www.mail-archive.com/freebsd-net@freebsd.org/msg11857.html RW> where a 10 minute keepalive from a Novell system defeated the FreeBSD RW> 11min 15 sec FIN_WAIT timeout. This situation is a bit different as RW> FreeBSD is the server rather than the client. I wonder if 195.248.160.78 RW> is a Novell system? RW> If it is similar, there's no real bug in the FreeBSD TCP stack, but the RW> far end is acting strangely with an abnormally fast keepalive. RW> It would be worth tcpdumping 195.248.160.78 traffic on those ports for RW> 30 mins or so to see if it is simply doing keepalives more frequently RW> that 12 mins. tcpdumping for 30 min shows now traffic from 195.248.160.78, only traffic to this host. -- Lucky carrier, Pavel.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040824131532.GA20828>