From owner-freebsd-stable@FreeBSD.ORG Tue Sep 14 10:37:36 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 7276B1065672 for ; Tue, 14 Sep 2010 10:37:36 +0000 (UTC) (envelope-from bsd@lordcow.org) Received: from lordcow.org (lordcow.org [41.203.5.188]) by mx1.freebsd.org (Postfix) with ESMTP id 8FC648FC1C for ; Tue, 14 Sep 2010 10:37:34 +0000 (UTC) Received: from lordcow.org (localhost [127.0.0.1]) by lordcow.org (8.14.4/8.14.4) with ESMTP id o8EAb3OB058550 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Tue, 14 Sep 2010 12:37:03 +0200 (SAST) (envelope-from lordcow@lordcow.org) Received: (from lordcow@localhost) by lordcow.org (8.14.4/8.14.4/Submit) id o8EAaw0F058549 for stable@freebsd.org; Tue, 14 Sep 2010 12:36:58 +0200 (SAST) (envelope-from lordcow) Date: Tue, 14 Sep 2010 12:36:57 +0200 From: Gareth de Vaux To: stable@freebsd.org Message-ID: <20100914103657.GA57521@lordcow.org> References: <20100909153902.GA28341@lordcow.org> <20100909162009.GA80375@icarus.home.lan> <20100910114908.GA55978@lordcow.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100910114908.GA55978@lordcow.org> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lordcow.org Cc: 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 10:37:36 -0000 On Fri 2010-09-10 (13:49), Gareth de Vaux wrote: > > Thirdly, if you feel FIN_WAIT2 is the cause of your problem, then you > > should consider adjusting the following sysctl: > > > > net.inet.tcp.finwait2_timeout > > > > Try something like 15000 (15 seconds) instead of the default (60000). > > Ok that seems to be doing something. Will report back later. Nope it's not helping. That and/or dropping net.inet.ip.fw.dyn_ack_lifetime.