From owner-freebsd-net@FreeBSD.ORG Sat Oct 27 04:07:02 2007 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8368D16A469; Sat, 27 Oct 2007 04:07:02 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 5B53D13C4A7; Sat, 27 Oct 2007 04:07:02 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id EB7383C7EA; Sat, 27 Oct 2007 00:07:01 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sat, 27 Oct 2007 00:07:01 -0400 X-Sasl-enc: FYNquJ6e6OOzafzQzyc3IjxDsqzM92oqznFJvgGslxRd 1193458021 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 44EA738FE; Sat, 27 Oct 2007 00:07:01 -0400 (EDT) Message-ID: <4722B964.5060701@FreeBSD.org> Date: Sat, 27 Oct 2007 05:07:00 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.6 (X11/20070928) MIME-Version: 1.0 To: Matus Harvan References: <20070909204148.GB18107@inf.ethz.ch> <20071026155206.GH1049@styx.ethz.ch> <4722B6A3.6030606@FreeBSD.org> In-Reply-To: <4722B6A3.6030606@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Brooks Davis , Max Laier Subject: Re: TCP listenall X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Oct 2007 04:07:02 -0000 Bruce M. Simpson wrote: > > The relay port idea I pointed out in my message about udp catchall > would be especially applicable here -- we may not always want > catchalls for the entire 16-bit tcp port space. > ... > How will inp_tlistenall appear in netstat output? Perhaps assigning a > LISTEN_ALL state would be helpful for an administrator to clearly see > that a listenall socket is active? Perhaps checking for TCP_LISTENALL > set on an unbound socket in tcp_usr_listen() when listen() is called > is the way to go instead of, or in addition to, using inp_tlistenall? P.S. This is probably how you get INET6 support for little cost. Hint hint. ;-) BMS