From owner-freebsd-net@FreeBSD.ORG Sun Apr 4 15:31:04 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 69B3616A4CE for ; Sun, 4 Apr 2004 15:31:04 -0700 (PDT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB92043D3F for ; Sun, 4 Apr 2004 15:31:01 -0700 (PDT) (envelope-from berhart@erhartgroup.com) Received: from cocaine.erhartgroup.com (c-67-166-0-138.client.comcast.net[67.166.0.138]) by comcast.net (sccrmhc11) with SMTP id <2004040422310001100c1gq4e>; Sun, 4 Apr 2004 22:31:01 +0000 Message-Id: <6.0.2.0.2.20040404163034.01c82c80@mx1.erhartgroup.com> X-Sender: berhart%erhartgroup.com@mx1.erhartgroup.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.2.0 Date: Sun, 04 Apr 2004 16:31:09 -0600 To: Chuck Swiger From: Brandon Erhart In-Reply-To: <40708B96.4050905@mac.com> References: <6.0.2.0.2.20040404152043.01c83320@mx1.erhartgroup.com> <4070860F.6030701@mac.com> <6.0.2.0.2.20040404160622.01c84428@mx1.erhartgroup.com> <40708B96.4050905@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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: Sun, 04 Apr 2004 22:31:04 -0000 I want to explicitly get it out of those states, without any help from the other end. What must I modify to achieve this? Brandon At 04:26 PM 4/4/2004, you wrote: >Brandon Erhart wrote: >[ ... ] >>Any advice on the timeouts? I don't really care about the RFC , honestly >>:-P. Like I said, I'm going for sheer speed. > >My advice was to read the RFC as it contains significant discussion about >these timeouts, but you're free to disregard it if you please. > >In particular, the discussion of FIN/ACK handling is relevant, since a TCP >implementation ought to move through the various FIN_WAIT states rapidly >if both sides agree to close and don't have more data to send. Using >tcpdump to verify what's going on might help you figure out why the >connections are lingering around... > >-- >-Chuck