From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick Jones Subject: Re: Finding a hidden bound TCP socket Date: Wed, 23 Nov 2011 13:38:15 -0800 Message-ID: <4ECD67C7.3010702@hp.com> References: <20111123.160143.58902472755124590.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: gdfuego@gmail.com, richard.weinberger@gmail.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org To: David Miller Return-path: In-Reply-To: <20111123.160143.58902472755124590.davem@davemloft.net> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On 11/23/2011 01:01 PM, David Miller wrote: > From: "G. D. Fuego" > Date: Wed, 23 Nov 2011 15:27:33 -0500 > >> Any comments? The behavior seems broken. At the very least its very >> inconsistent with other Unixes. > > Until the socket has a full final tuple it is bound to, there is no > reason to list it. > > No UNIX lists a socket which is partially bound and hasn't either > performed a listen() or a connect(). Well.... I took the .c file mentioned previously, and compiled it on a Solaris 10 8/11 instance. The 25-odd sockets it created *were* listed in the output of netstat -an -- local address as *. remote address as *.* and a state of "BOUND." A FreeBSD (rev 8 IIRC) netstat -an seems to display them in a state of "CLOSED." I didn't check HP-UX 11i v3 or AIX 6. rick jones