From owner-freebsd-net@FreeBSD.ORG Tue Oct 12 01:38:32 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 C4CFA16A4CE for ; Tue, 12 Oct 2004 01:38:32 +0000 (GMT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 36DD143D1D for ; Tue, 12 Oct 2004 01:38:32 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 66216 invoked from network); 12 Oct 2004 01:38:31 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 12 Oct 2004 01:38:31 -0000 X-pair-Authenticated: 209.68.2.70 Date: Mon, 11 Oct 2004 20:38:29 -0500 (CDT) From: Mike Silbersack To: Eli Dart In-Reply-To: <20041011181026.35775F987@gemini.nersc.gov> Message-ID: <20041011203609.N77693@odysseus.silby.com> References: <20041011181026.35775F987@gemini.nersc.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-net@freebsd.org cc: Omer Faruk Sen Subject: Re: time X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Oct 2004 01:38:32 -0000 On Mon, 11 Oct 2004, Eli Dart wrote: > > In reply to Omer Faruk Sen : > >> According to the very old article stated >> http://www.totse.com/en/technology/computer_technology/162444.html there is >> no way to tune time_wait timeout in FreeBSD. But since it is very old >> article my question is this: >> >> Is there a way to change the time_wait timeout value in FreeBSD? > > sysctl -w net.inet.tcp.msl= > > The default is 30000 (30 seconds). > > --eli That may have other sideeffects, however. In FreeBSD 5.x, the TIME_WAIT timeout is not configurable, but time_wait sockets are stored in a seperate hash table. Also, they are now terminated prematurely when there is a shortage of ephemeral ports. As a result, time_wait sockets are no longer the problem they were in certain situations under 4.x. Mike "Silby" Silbersack