From: Phil Sutter <phil@nwl.cc>
To: Hagen Paul Pfeifer <hagen@jauu.net>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: netstat and dual stack sockets
Date: Tue, 16 Jun 2015 03:25:53 +0200 [thread overview]
Message-ID: <20150616012538.05160213DD@mail.nwl.cc> (raw)
In-Reply-To: <CAPh34mdX2YuqMVY8Adjnaa4CET2xaMJafQ2mLgck6sOo0Nq3xQ@mail.gmail.com>
HGN!
On Mon, Jun 15, 2015 at 11:36:54PM +0200, Hagen Paul Pfeifer wrote:
> On 15 June 2015 at 22:54, Phil Sutter <phil@nwl.cc> wrote:
>
> > As I see it, a user has no way of detecting the listening socket in this
> > address family: it does not show in /proc/net/{tcp,udp} nor do
> > 'netstat', 'ss' or 'lsof' print any additional information about those
> > sockets over pure IPv6 ones.
>
> Probably a combination of IPV6_V6ONLY(1, 0) and IN6_IS_ADDR_V4MAPPED
> fulfills all user requirements, ... so far. Your proposal is to hand
> over sk->sk_ipv6only?
Not sure if I understand you correctly - of course it is possible to
programmatically determine whether a socket one has opened accepts
v4mapped addresses or a given address is v4mapped. My concern is about
the system administrator's point of view, using system tools to find out
on which IP addresses and ports a machine is accessible. Looking at e.g.
/proc/net/tcp6 does not reveal if a listening socket also accepts
v4mapped addresses, factually acting as AF_INET socket upon request.
Cheers, Phil
next prev parent reply other threads:[~2015-06-16 1:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 20:54 netstat and dual stack sockets Phil Sutter
2015-06-15 21:36 ` Hagen Paul Pfeifer
2015-06-16 1:25 ` Phil Sutter [this message]
2015-06-19 12:15 ` [PATCH] net: inet_diag: export IPV6_V6ONLY sockopt Phil Sutter
2015-06-19 13:52 ` Eric Dumazet
2015-06-21 1:47 ` Phil Sutter
2015-06-21 8:52 ` 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=20150616012538.05160213DD@mail.nwl.cc \
--to=phil@nwl.cc \
--cc=hagen@jauu.net \
--cc=netdev@vger.kernel.org \
/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).