From owner-freebsd-bugs Fri Nov 1 12:59:52 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA08617 for bugs-outgoing; Fri, 1 Nov 1996 12:59:52 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA08593 for ; Fri, 1 Nov 1996 12:59:47 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <16386(1)>; Fri, 1 Nov 1996 12:52:33 PST Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177554>; Fri, 1 Nov 1996 11:07:29 -0800 X-Mailer: exmh version 1.6.7 5/3/96 To: Peter Wemm cc: freebsd-bugs@freefall.freebsd.org Subject: Re: kern/1940: TCP doesn't time out of FIN_WAIT_1 and floods packets. In-reply-to: Your message of "Fri, 01 Nov 1996 02:10:02 PST." <199611011010.CAA14999@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 1 Nov 1996 11:07:24 PST From: Bill Fenner Message-Id: <96Nov1.110729pst.177554@crevenia.parc.xerox.com> Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199611011010.CAA14999@freefall.freebsd.org>you write: > It's a little hard to > see for sure, since tcpdump had made the seq/ack's relative.. For future reference, a good thing to do in situations like this is to write the raw data to a file, using "tcpdump -w /tmp/foo ..."; then you can go back to it and do a "tcpdump -x" on it to read the actual packet, or you can let tcpdump interpret things. It looks like tcpdump got confused by seeing the fin as the first packet. Bill