From owner-freebsd-net Thu Mar 6 18:29:59 2003 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 6F15637B401 for ; Thu, 6 Mar 2003 18:29:58 -0800 (PST) Received: from exchange.wan.no (exchange.wan.no [80.86.128.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EA8943FB1 for ; Thu, 6 Mar 2003 18:29:57 -0800 (PST) (envelope-from sten.daniel.sorsdal@wan.no) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: TCP in TIME_WAIT for too long? X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Fri, 7 Mar 2003 03:29:51 +0100 Message-ID: <0AF1BBDF1218F14E9B4CCE414744E70F07DE6B@exchange.wanglobal.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: TCP in TIME_WAIT for too long? Thread-Index: AcLkUVQLyvKNSuJSQI+t7c8cy5t++A== From: =?iso-8859-1?Q?Sten_Daniel_S=F8rsdal?= To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've tried freebsd-questions but no reply. I use a FreeBSD 4.7-STABLE box as a Zebra BGP route server. When my provider reset their interface (switch inbetween) the=20 TCP connect seems to linger in TIME_WAIT for a very long time (up to 20 minutes?). Are there any ways to tweak the TCP settings to detect a dead tcp connect in just a manner of minutes/seconds? - Sten To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message