From owner-freebsd-net Fri Feb 21 16:10: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 6889B37B401 for ; Fri, 21 Feb 2003 16:10:48 -0800 (PST) Received: from odysseus.silby.com (d45.as8.nwbl0.wi.voyager.net [169.207.132.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2C1043FDD for ; Fri, 21 Feb 2003 16:10:46 -0800 (PST) (envelope-from silby@silby.com) Received: from odysseus.silby.com (localhost [127.0.0.1]) by odysseus.silby.com (8.12.7/8.12.7) with ESMTP id h1M07sJZ001084; Fri, 21 Feb 2003 18:07:54 -0600 (CST) (envelope-from silby@silby.com) Received: from localhost (silby@localhost) by odysseus.silby.com (8.12.7/8.12.7/Submit) with ESMTP id h1M07mbl001081; Fri, 21 Feb 2003 18:07:54 -0600 (CST) X-Authentication-Warning: odysseus.silby.com: silby owned process doing -bs Date: Fri, 21 Feb 2003 18:07:48 -0600 (CST) From: Mike Silbersack To: Steve Shorter Cc: freebsd-net@freebsd.org Subject: Re: TCP stuck in LAST_ACK in 4.5 and 4.6?? In-Reply-To: <20030221151701.A9389@nomad.lets.net> Message-ID: <20030221175707.Y1033@odysseus.silby.com> References: <20030221151701.A9389@nomad.lets.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Fri, 21 Feb 2003, Steve Shorter wrote: > 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 The answer is: I do not know for sure, I have not done sufficient testing to prove the nonexistence of the problem. However, what I can share with you is this snippet of a conversation about the problem I had back in October: --- From: G.P. de Boer To: Mike Silbersack Subject: The "stale TCP-connects in LAST_ACK" problem Hi Mike, I've upgraded my system to 4.7-STABLE as you said, to see if the patches Matt Dillon MFC'ed made my problem disappear. I have good news: with a current uptime of more than 4 days I have no single stale connection in the LAST_ACK state. On 4.6.2 I have seen a number of stale connections starting from about 3 days of uptime; From this I conclude (a vulcan would kill me for such reasoning though) it's fixed. --- So, I would suggest that you update to 4.7-stable. If that's not an option, I can look back and see if I can figure out which patches in question I was referring to at the time. Sorry that I can't give you a more concrete answer. Dillon's changes weren't meant to fix the LAST_ACK problem, but they ended up doing so for G.P. de Boer. I would be very interested in hearing if they have the same effect for you. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message