From owner-freebsd-net@FreeBSD.ORG Mon Apr 5 15:09:41 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 B7C5E16A4CE for ; Mon, 5 Apr 2004 15:09:41 -0700 (PDT) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE34643D53 for ; Mon, 5 Apr 2004 15:09:40 -0700 (PDT) (envelope-from andre@freebsd.org) Received: (qmail 72460 invoked from network); 5 Apr 2004 22:09:39 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 5 Apr 2004 22:09:39 -0000 Message-ID: <4071D923.A7E0D93F@freebsd.org> Date: Tue, 06 Apr 2004 00:09:39 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Brandon Erhart References: <20040405171756.90E3BF8F2@gemini.nersc.gov> <6.0.2.0.2.20040405133109.01c755c8@mx1.erhartgroup.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: FIN_WAIT_[1,2] and LAST_ACK 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: Mon, 05 Apr 2004 22:09:41 -0000 Brandon Erhart wrote: > > Well, I responded to the group that I had taken one of the fellows advice > posting here, and modified the tcp_usrclosed in netinet/tcp_usrreq.c. > > So all is well -- it gets TCPS_CLOSED state and the tcps_close() function > called on the tuple IMMEDIATELY. It doesn't switch states depending on > which state the connection is currently in. I also made a sysctl variable > for it (to turn the "feature" on or off), and will post the small patch > along w/ some other small changes I have made soon. As far as I am aware (I was looking through and testing the FIN_WAIT states in 5.2 around last christmas) our TCP stack is behaving correctly. Do the FIN_WAIT_1|2 and LAST_ACK time out after 2MSL or do they stick around forever? If they stick around forever, then there is something broken. But I suspect you are just running out of the small space of local ports with your application as I said in the previous email. -- Andre > Thanks, > > Brandon > > At 11:17 AM 4/5/2004, you wrote: > > >In reply to Brandon Erhart : > > > > > Hello everyone, > > > > > However, I have run into a new problem. I am getting a good amount of > > > blocks stuck in FIN_WAIT_1, FIN_WAIT_2 or LAST_ACK that stick around for a > > > long while. > > > >Could you define "long" in this case? Are we talking about 60 > >seconds, or 60 minutes? I get the feeling that your requirements > >might make your perception of "long" different from others' notion of > >"long." > > > >The reason I ask is that there was a bug once upon a time that made > >some connections stick in LAST_ACK forever.... > > > > --eli > > > > > > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"