From owner-freebsd-hackers Tue Sep 4 21:12:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 9C85A37B406 for ; Tue, 4 Sep 2001 21:12:44 -0700 (PDT) Received: (qmail 8107 invoked by uid 1000); 5 Sep 2001 04:12:43 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 Sep 2001 04:12:43 -0000 Date: Tue, 4 Sep 2001 23:12:43 -0500 (CDT) From: Mike Silbersack To: Terry Lambert Cc: "Vladimir A. Jakovenko" , , Subject: Re: SO_REUSEPORT on unicast UDP sockets In-Reply-To: <3B947922.F8B98DBD@mindspring.com> Message-ID: <20010904231049.E7815-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 3 Sep 2001, Terry Lambert wrote: > Similarly, there are a number of bugs in the TCP sockets as > well; specifically, there's a problem with all sockets being > treated as being in the same collision domain, when doing > automatic port assignment. This limits you to 65535 oubound > TCP connections, even though you have multiple IP aliases on > an interface (theoretically, you should get 64k connections > per IP address, if you bind _not_ to IN_ADDR_ANY, but instead > use a specific port, but the hash is broken). I like this problem's evil sibling: client side TIME_WAITs. If you build them up, you just sit there unable to allocate outgoing ports until they time out. Maybe net or openbsd handle these situations better, I'll have to check later. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message