From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Sutter Subject: Re: [iproute2] regression in ss output Date: Wed, 18 Oct 2017 19:11:16 +0200 Message-ID: <20171018171116.GC32305@orbyte.nwl.cc> References: <20171016103320.GP11332@orbyte.nwl.cc> <20171016142807.47825131@xeon-e3> <1508205636.31614.81.camel@edumazet-glaptop3.roam.corp.google.com> <20171016194958.669625db@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Eric Dumazet , Humberto Alves , netdev@vger.kernel.org To: Stephen Hemminger Return-path: Received: from orbyte.nwl.cc ([151.80.46.58]:47458 "EHLO orbyte.nwl.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750853AbdJRRLS (ORCPT ); Wed, 18 Oct 2017 13:11:18 -0400 Content-Disposition: inline In-Reply-To: <20171016194958.669625db@xeon-e3> Sender: netdev-owner@vger.kernel.org List-ID: On Mon, Oct 16, 2017 at 07:49:58PM -0700, Stephen Hemminger wrote: > On Mon, 16 Oct 2017 19:00:36 -0700 > Eric Dumazet wrote: > > > On Mon, 2017-10-16 at 14:28 -0700, Stephen Hemminger wrote: > > > On Mon, 16 Oct 2017 20:44:07 +0000 > > > Humberto Alves wrote: > > > > > > > Yes, just get rid of this 'if statement'. > > > > in6addr_any should be represented as '::', not '*'. Otherwise it's > > > > impossible to distinguish IPv4 listening addresses from IPv6. Thank you :) > > > > > > But IPv6 accepts IPv4 as well. > > > > Not always (IPV6_V6ONLY socket option) > > > > I agree that this recent change in ss is problematic. > > > > Please give us back a way to distinguish IPV6 and IPv4 > > What about > *:80 << both IPV6 and IPV4 > [::]:80 << IPV6_ONLY > 0.0.0.0:80 << IPV4_ONLY Assuming that this will be distinguished based on INET_DIAG_SKV6ONLY attribute, tc will then use the asterisk for v6only sockets on older kernels not supporting the feature. Fine with me, just a heads-up! Cheers, Phil