From owner-freebsd-hackers Wed Jan 10 16:03:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA13994 for hackers-outgoing; Wed, 10 Jan 1996 16:03:11 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA13988 Wed, 10 Jan 1996 16:03:06 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <16367(7)>; Wed, 10 Jan 1996 16:00:39 PST Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177478>; Wed, 10 Jan 1996 15:59:41 -0800 X-Mailer: exmh version 1.6.4 10/10/95 To: Michael Smith cc: taob@io.org (Brian Tao), freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org Subject: Re: A few other concerns from a FreeBSD ISP In-reply-to: Your message of "Sun, 07 Jan 1996 02:54:31 PST." <199601071054.VAA20347@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Jan 1996 15:59:29 PST From: Bill Fenner Message-Id: <96Jan10.155941pst.177478@crevenia.parc.xerox.com> Sender: owner-hackers@freebsd.org Precedence: bulk In message <199601071054.VAA20347@genesis.atrad.adelaide.edu.au>you write: >It's possible that the remote host is reusing an originating port number >that is still recorded by the FreeBSD system as belonging to a connection >in one of the closing wait states to that same host. I don't know what >would happen here, it's possible that someone got their TCP state diagram >confused. I have always thought that this situation could only be attributed to one or the other end not waiting for 2*MSL before deleting connection information. In particular, if the source end cut its TIME_WAIT state short for some tcpcb, that port number could get reused while the server end was still in TIME_WAIT and thus completely ignoring all packets. But I haven't yet gotten around to testing this theory; I can't say that I recall seeing this problem, so it may also be load-related, etc. Bill