From owner-freebsd-net@FreeBSD.ORG Tue Aug 24 13:15:34 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32B1616A4CF for ; Tue, 24 Aug 2004 13:15:34 +0000 (GMT) Received: from happy.kiev.ua (happy.kiev.ua [193.109.241.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDD9F43D1D for ; Tue, 24 Aug 2004 13:15:33 +0000 (GMT) (envelope-from gul@happy.kiev.ua) Received: from gul by happy.kiev.ua with local (Exim 4.41) id 1Bzb9A-0007wW-BY; Tue, 24 Aug 2004 16:15:32 +0300 Date: Tue, 24 Aug 2004 16:15:32 +0300 From: Pavel Gulchouck To: Richard Wendland Message-ID: <20040824131532.GA20828@happy.kiev.ua> References: <412B1883.9C3E38C2@freebsd.org> <200408241129.i7OBTg917650@starburst.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408241129.i7OBTg917650@starburst.demon.co.uk> X-Operating-System: Linux X-FTN-Address: 2:463/68 X-Flames-To: /dev/null X-GC: GCC d- s+: a33 C+++ UL++++ UB++++ P+ L++ E--- W++ N++ o-- K- w--- O++ X-GC: M? V- PS PE+ Y+ PGP+ t? 5? X? R? !tv b+ DI? D? G e h--- r+++ y+++ User-Agent: Mutt/1.5.6i cc: freebsd-net@freebsd.org Subject: Re: FIN_WAIT_2 timeout X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: gul@gul.kiev.ua List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Aug 2004 13:15:34 -0000 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.