From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: gdfuego@gmail.com, richard.weinberger@gmail.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Finding a hidden bound TCP socket
Date: Wed, 23 Nov 2011 13:38:15 -0800 [thread overview]
Message-ID: <4ECD67C7.3010702@hp.com> (raw)
In-Reply-To: <20111123.160143.58902472755124590.davem@davemloft.net>
On 11/23/2011 01:01 PM, David Miller wrote:
> From: "G. D. Fuego"<gdfuego@gmail.com>
> 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 *.<portnum> 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
next prev parent reply other threads:[~2011-11-23 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALmbKGV0g2nfNAghF5dGrt=TCyrms6RznOL8jSkg+gkgyfekLg@mail.gmail.com>
2011-11-15 20:23 ` Finding a hidden bound TCP socket richard -rw- weinberger
2011-11-23 20:27 ` G. D. Fuego
2011-11-23 20:32 ` Eric Dumazet
2011-11-23 21:01 ` David Miller
2011-11-23 21:38 ` Rick Jones [this message]
2011-11-24 21:31 ` richard -rw- weinberger
2011-11-24 21:53 ` Eric Dumazet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ECD67C7.3010702@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=gdfuego@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).