From: Stephen Hemminger <stephen@networkplumber.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netdev@vger.kernel.org, Humberto Alves <hjalves@live.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [iproute PATCH] ss: Distinguish between IPv4 and IPv6 wildcard sockets
Date: Mon, 23 Oct 2017 14:41:42 +0200 [thread overview]
Message-ID: <20171023144142.7496e791@shemminger-XPS-13-9360> (raw)
In-Reply-To: <20171018175813.5387-1-phil@nwl.cc>
On Wed, 18 Oct 2017 19:58:13 +0200
Phil Sutter <phil@nwl.cc> wrote:
> Commit aba9c23a6e1cb ("ss: enclose IPv6 address in brackets") unified
> display of wildcard sockets in IPv4 and IPv6 to print the unspecified
> address as '*'. Users then complained that they can't distinguish
> between address families anymore, so change this again to what Stephen
> Hemminger suggested:
>
> | *:80 << both IPV6 and IPV4
> | [::]:80 << IPV6_ONLY
> | 0.0.0.0:80 << IPV4_ONLY
>
> Note that on older kernels which don't support INET_DIAG_SKV6ONLY
> attribute, pure IPv6 sockets will still show as '*'.
>
> Cc: Humberto Alves <hjalves@live.com>
> Cc: Eric Dumazet <eric.dumazet@gmail.com>
> Signed-off-by: Phil Sutter <phil@nwl.cc>
Applied both.
next prev parent reply other threads:[~2017-10-23 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 9:57 [iproute2] regression in ss output Humberto Alves
2017-10-16 10:33 ` Phil Sutter
2017-10-16 20:44 ` Humberto Alves
2017-10-16 21:28 ` Stephen Hemminger
2017-10-17 2:00 ` Eric Dumazet
[not found] ` <20171016194958.669625db@xeon-e3>
2017-10-18 14:08 ` Humberto Alves
2017-10-18 14:17 ` Eric Dumazet
2017-10-18 17:11 ` Phil Sutter
2017-10-18 17:58 ` [iproute PATCH] ss: Distinguish between IPv4 and IPv6 wildcard sockets Phil Sutter
2017-10-23 12:41 ` Stephen Hemminger [this message]
2017-10-16 16:20 ` [iproute2] regression in ss output Stephen Hemminger
2017-10-16 20:34 ` Humberto Alves
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=20171023144142.7496e791@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.org \
--cc=eric.dumazet@gmail.com \
--cc=hjalves@live.com \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
/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