netdev - Re: [PATCH iproute2-next] ipneigh: add support to print brief output of neigh cache in tabular format

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <390278ce-2405-ae9e-9b07-ea8c699d762c@gmail.com>
Date:   Mon, 26 Jul 2021 15:09:01 -0600
From:   David Ahern <dsahern@...il.com>
To:     Gokul Sivakumar <gokulkumar792@...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 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.

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.