From owner-freebsd-net@FreeBSD.ORG Tue Aug 24 12:12:03 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 E933416A4D2; Tue, 24 Aug 2004 12:12:03 +0000 (GMT) Received: from starburst.demon.co.uk (starburst.demon.co.uk [80.176.229.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1DDB43D45; Tue, 24 Aug 2004 12:11:11 +0000 (GMT) (envelope-from richard@starburst.demon.co.uk) Received: (from richard@localhost) by starburst.demon.co.uk (8.11.6/8.11.6) id i7OBTg917650; Tue, 24 Aug 2004 12:29:42 +0100 From: Richard Wendland Message-Id: <200408241129.i7OBTg917650@starburst.demon.co.uk> To: andre@freebsd.org (Andre Oppermann) Date: Tue, 24 Aug 2004 12:29:42 +0100 (BST) In-Reply-To: <412B1883.9C3E38C2@freebsd.org> from "Andre Oppermann" at Aug 24, 2004 12:29:23 X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: gul@gul.kiev.ua Subject: Re: FIN_WAIT_2 timeout X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: richard@codeburst.co.uk 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 12:12:04 -0000 > > 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... This is somewhat similar to a problem I explained a few months back: http://www.mail-archive.com/freebsd-net@freebsd.org/msg11857.html where a 10 minute keepalive from a Novell system defeated the FreeBSD 11min 15 sec FIN_WAIT timeout. This situation is a bit different as FreeBSD is the server rather than the client. I wonder if 195.248.160.78 is a Novell system? If it is similar, there's no real bug in the FreeBSD TCP stack, but the far end is acting strangely with an abnormally fast keepalive. It would be worth tcpdumping 195.248.160.78 traffic on those ports for 30 mins or so to see if it is simply doing keepalives more frequently that 12 mins. Richard -- Richard Wendland richard@codeburst.co.uk