From owner-freebsd-stable@FreeBSD.ORG Tue Sep 14 11:30:56 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12A24106566B for ; Tue, 14 Sep 2010 11:30:56 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by mx1.freebsd.org (Postfix) with ESMTP id B21DD8FC1A for ; Tue, 14 Sep 2010 11:30:55 +0000 (UTC) Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta02.westchester.pa.mail.comcast.net with comcast id 6bLj1f0041vXlb852bWv72; Tue, 14 Sep 2010 11:30:55 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta17.westchester.pa.mail.comcast.net with comcast id 6bWu1f00Q3LrwQ23dbWvoP; Tue, 14 Sep 2010 11:30:55 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 48E879B423; Tue, 14 Sep 2010 04:30:53 -0700 (PDT) Date: Tue, 14 Sep 2010 04:30:53 -0700 From: Jeremy Chadwick To: Gareth de Vaux Message-ID: <20100914113053.GA19053@icarus.home.lan> References: <20100909153902.GA28341@lordcow.org> <20100909162009.GA80375@icarus.home.lan> <20100910114908.GA55978@lordcow.org> <20100914103657.GA57521@lordcow.org> <20100914110302.GA84971@icarus.home.lan> <20100914111200.GA59889@lordcow.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100914111200.GA59889@lordcow.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: stable@freebsd.org, luigi@freebsd.org Subject: Re: ipfw: Too many dynamic rules X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2010 11:30:56 -0000 On Tue, Sep 14, 2010 at 01:12:00PM +0200, Gareth de Vaux wrote: > On Tue 2010-09-14 (04:03), Jeremy Chadwick wrote: > > You're absolutely certain these are all in FIN_WAIT_2 state and not > > TIME_WAIT? > > Yup, > > $ netstat -an | grep FIN_WAIT_1 | wc -l > 57 > $ netstat -an | grep FIN_WAIT_2 | wc -l > 431 > $ netstat -an | grep TIME_WAIT | wc -l > 17 Regarding net.inet.tcp.finwait2_timeout=15000 -- you don't see any improvement at all? That's a bit strange. There's probably something about ipfw I'm not getting. Adding luigi@ to the CC list, since I think he's familiar with ipfw internals. FWIW, I'd recommend keeping an appended log of output from something like this script: while true do echo "`date` -- `netstat -n | grep -c FIN_WAIT_2`" >> /some/log sleep 5 done Just make sure the sleep interval is lower than the FIN timeout. Another thing to try: setting net.inet.tcp.fast_finwait2_recycle=1 and see if this makes a difference. I'm not familiar with this setting myself, but some Google results indicate some people do use it. The sysctl description is a bit vague too. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |