From owner-freebsd-net@FreeBSD.ORG  Fri Oct 31 20:25:00 2003
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 91B6E16A4CE
	for <freebsd-net@freebsd.org>; Fri, 31 Oct 2003 20:25:00 -0800 (PST)
Received: from relay.pair.com (relay.pair.com [209.68.1.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 943EB43F75
	for <freebsd-net@freebsd.org>; Fri, 31 Oct 2003 20:24:59 -0800 (PST)
	(envelope-from silby@silby.com)
Received: (qmail 1377 invoked from network); 1 Nov 2003 04:24:58 -0000
Received: from niwun.pair.com (HELO localhost) (209.68.2.70)
  by relay.pair.com with SMTP; 1 Nov 2003 04:24:58 -0000
X-pair-Authenticated: 209.68.2.70
Date: Fri, 31 Oct 2003 22:24:56 -0600 (CST)
From: Mike Silbersack <silby@silby.com>
To: Bruce M Simpson <bms@spc.org>
In-Reply-To: <20031028131329.J19707@odysseus.silby.com>
Message-ID: <20031031222225.E54781@odysseus.silby.com>
References: <20031027014854.K2023@odysseus.silby.com>
	<20031028131329.J19707@odysseus.silby.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-net@freebsd.org
Subject: Re: Changes to PCBPORTHASH wrt TCP, review needed
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Nov 2003 04:25:00 -0000


On Tue, 28 Oct 2003, Mike Silbersack wrote:

> It's very possible that bind will return a port which can't be used
> because it's already in use for that destination lport-laddr-fport-faddr
> tuple, so the connect will fail with EADDRINUSE.
>
> So, it looks like I can't solve this so simply... looks like I'll have to
> have the port lookup do IP comparisons as well.
>
> Mike "Silby" Silbersack

After more thought, I've come to the conclusion that it's not easy to do
away with the lport hash, and that changes would only benefit certain
applications.  So, I've given up on the lport reuse issue and refocused on
the problem of time_wait sockets clogging up all local ports under certain
situations.  I did manage to find a good solution for that problem, and
it'll be committed pretty soon.

Mike "Silby" Silbersack