Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Gokul Sivakumar <gokulkumar792@gmail.com>
To: David Ahern <dsahern@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] ipneigh: add support to print brief output of neigh cache in tabular format
Date: Tue, 27 Jul 2021 22:03:48 +0530	[thread overview]
Message-ID: <b9f79fa651c025456b1cd8b071210480b0733348.camel@gmail.com> (raw)
In-Reply-To: <390278ce-2405-ae9e-9b07-ea8c699d762c@gmail.com>

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.


      reply	other threads:[~2021-07-27 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-25 15:39 Gokul Sivakumar
2021-07-26 21:09 ` David Ahern
2021-07-27 16:33   ` Gokul Sivakumar [this message]

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=b9f79fa651c025456b1cd8b071210480b0733348.camel@gmail.com \
    --to=gokulkumar792@gmail.com \
    --cc=dsahern@gmail.com \
    --cc=netdev@vger.kernel.org \
    --subject='Re: [PATCH iproute2-next] ipneigh: add support to print brief output of neigh cache in tabular format' \
    /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

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).