From owner-freebsd-net Fri Feb 21 12:22:51 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 50CE137B401 for ; Fri, 21 Feb 2003 12:22:50 -0800 (PST) Received: from spitfire.velocet.net (spitfire.velocet.net [216.138.223.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id E31BA43F85 for ; Fri, 21 Feb 2003 12:22:49 -0800 (PST) (envelope-from steve@nomad.tor.lets.net) Received: from nomad.tor.lets.net (H74.C220.tor.velocet.net [216.138.220.74]) by spitfire.velocet.net (Postfix) with SMTP id 17A9B4B7D95 for ; Fri, 21 Feb 2003 15:22:48 -0500 (EST) Received: (qmail 9398 invoked by uid 1001); 21 Feb 2003 20:17:01 -0000 Date: Fri, 21 Feb 2003 15:17:01 -0500 From: Steve Shorter To: freebsd-net@freebsd.org Subject: Re: TCP stuck in LAST_ACK in 4.5 and 4.6?? Message-ID: <20030221151701.A9389@nomad.lets.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i 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 This is PR kern/25986 which is still open. Apparently, it can be interpreted as a bug in the TCP protocol. Is there work around this or do I just have to crank up maxsockets and reboot the machine every now and then like my old NT server :-) -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message