From: Stephen Hemminger <stephen@networkplumber.org>
To: Humberto Alves <hjalves@live.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [iproute2] regression in ss output
Date: Mon, 16 Oct 2017 09:20:58 -0700 [thread overview]
Message-ID: <20171016092058.470f3424@xeon-e3> (raw)
In-Reply-To: <AM4PR0901MB125261BF480B49D2BA2DF46BCC480@AM4PR0901MB1252.eurprd09.prod.outlook.com>
On Fri, 13 Oct 2017 09:57:37 +0000
Humberto Alves <hjalves@live.com> wrote:
> Hi! With the last iproute2 release, ss command output does not
> differentiate between any-address IPv4 sockets from the IPv6 ones.
> I don't know if this is an expected behaviour, but the old output looks
> more useful. Below I pasted the difference between the old behaviour and
> the new one.
> I am happy to send a patch if you want. Thanks
>
>
> iproute2-4.12
> -------------
>
> $ ss --version
> ss utility, iproute2-ss170705
>
> $ ss -ntl
> State Recv-Q Send-Q Local Address:Port Peer
> Address:Port
> LISTEN 0 100 *:587 *:*
>
> LISTEN 0 100 *:110 *:*
>
> LISTEN 0 100 *:143 *:*
>
> LISTEN 0 128 *:80 *:*
>
> LISTEN 0 128 *:2225 *:*
>
> LISTEN 0 10 127.0.0.1:5010 *:*
>
> LISTEN 0 128 *:20 *:*
>
> LISTEN 0 128 127.0.0.1:20150 *:*
>
> LISTEN 0 128 *:61719 *:*
>
> LISTEN 0 100 *:25 *:*
>
> LISTEN 0 3 *:1723 *:*
>
> LISTEN 0 128 *:17500 *:*
>
> LISTEN 0 128 127.0.0.1:17600 *:*
>
> LISTEN 0 128 *:8000 *:*
>
> LISTEN 0 100 *:993 *:*
>
> LISTEN 0 128 127.0.0.1:17603 *:*
>
> LISTEN 0 100 *:995 *:*
>
> LISTEN 0 100 :::587 :::*
>
> LISTEN 0 100 :::110 :::*
>
> LISTEN 0 100 :::143 :::*
>
> LISTEN 0 128 :::22000 :::*
>
> LISTEN 0 128 :::80 :::*
>
> LISTEN 0 128 :::2225 :::*
>
> LISTEN 0 128 :::20 :::*
>
> LISTEN 0 128 ::1:20150 :::*
>
> LISTEN 0 100 :::25 :::*
>
> LISTEN 0 128 :::17500 :::*
>
> LISTEN 0 128 :::8384 :::*
>
> LISTEN 0 100 :::993 :::*
>
> LISTEN 0 100 :::995 :::*
>
> iproute2-4.13
> -------------
>
> $ ss --version
> ss utility, iproute2-ss170905
>
> $ ss -ntl
> State Recv-Q Send-Q Local Address:Port Peer
> Address:Port
> LISTEN 0 100 *:587 *:*
>
> LISTEN 0 100 *:110 *:*
>
> LISTEN 0 100 *:143 *:*
>
> LISTEN 0 128 *:80 *:*
>
> LISTEN 0 128 *:2225 *:*
>
> LISTEN 0 10 127.0.0.1:5010 *:*
>
> LISTEN 0 128 *:20 *:*
>
> LISTEN 0 128 127.0.0.1:20150 *:*
>
> LISTEN 0 128 *:61719 *:*
>
> LISTEN 0 100 *:25 *:*
>
> LISTEN 0 3 *:1723 *:*
>
> LISTEN 0 128 *:17500 *:*
>
> LISTEN 0 128 127.0.0.1:17600 *:*
>
> LISTEN 0 128 *:8000 *:*
>
> LISTEN 0 100 *:993 *:*
>
> LISTEN 0 128 127.0.0.1:17603 *:*
>
> LISTEN 0 100 *:995 *:*
>
> LISTEN 0 100 *:587 *:*
>
> LISTEN 0 100 *:110 *:*
>
> LISTEN 0 100 *:143 *:*
>
> LISTEN 0 128 *:22000 *:*
>
> LISTEN 0 128 *:80 *:*
>
> LISTEN 0 128 *:2225 *:*
>
> LISTEN 0 128 *:20 *:*
>
> LISTEN 0 128 [::1]:20150 *:*
>
> LISTEN 0 100 *:25 *:*
>
> LISTEN 0 128 *:17500 *:*
>
> LISTEN 0 128 *:8384 *:*
>
> LISTEN 0 100 *:993 *:*
>
> LISTEN 0 100 *:995 *:*
All changes are not regressions.
Yes it was intentional because the outputing [::]:20 looked ugly and using * makes IPv4 and IPv6
look the same.
next prev parent reply other threads:[~2017-10-16 16:21 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
2017-10-16 16:20 ` Stephen Hemminger [this message]
2017-10-16 20:34 ` [iproute2] regression in ss output 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=20171016092058.470f3424@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=hjalves@live.com \
--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).