[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b9f79fa651c025456b1cd8b071210480b0733348.camel@gmail.com>
Date: Tue, 27 Jul 2021 22:03:48 +0530
From: Gokul Sivakumar <gokulkumar792@...il.com>
To: David Ahern <dsahern@...il.com>, netdev@...r.kernel.org
Subject: Re: [PATCH iproute2-next] ipneigh: add support to print brief
output of neigh cache in tabular format
On Mon, 2021-07-26 at 15:09 -0600, David Ahern wrote:
> On 7/25/21 9:39 AM, Gokul Sivakumar wrote:
> > Make use of the already available brief flag and print the basic details of
> > the IPv4 or IPv6 neighbour cache in a tabular format for better readability
> > when the brief output is expected.
> >
> > $ ip -br neigh
> > bridge0 172.16.12.100 b0:fc:36:2f:07:43
> > bridge0 172.16.12.174 8c:16:45:2f:bc:1c
> > bridge0 172.16.12.250 04:d9:f5:c1:0c:74
> > bridge0 fe80::267b:9f70:745e:d54d b0:fc:36:2f:07:43
> > bridge0 fd16:a115:6a62:0:8744:efa1:9933:2c4c 8c:16:45:2f:bc:1c
> > bridge0 fe80::6d9:f5ff:fec1:c74 04:d9:f5:c1:0c:74
>
> I am guessing you put the device first to be consistent with the output
> for the other 2 commands.
Yes, that was my initial thought.
> In this case I think the network address should be first then device and
> lladdr which is consistent with existing output just removing 'dev'
> keyword and flags.
I understand, will send an updated v2 patch now to print the brief output with
columns in the order that you are suggesting.
Thanks.
Powered by blists - more mailing lists