netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Roopa Prabhu <roopa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, nikhil@cumulusnetworks.com,
	nikolay@cumulusnetworks.com
Subject: Re: [PATCH iproute2 net-next] bridge: this patch adds json support for bridge mdb show
Date: Tue, 18 Jul 2017 17:33:51 -0700	[thread overview]
Message-ID: <20170718173351.55cb566a@xeon-e3> (raw)
In-Reply-To: <1499466256-13808-1-git-send-email-roopa@cumulusnetworks.com>

On Fri,  7 Jul 2017 15:24:16 -0700
Roopa Prabhu <roopa@cumulusnetworks.com> wrote:

> From: Nikhil Gajendrakumar <nikhil@cumulusnetworks.com>
> 
> This patch adds json output to bridge mdb show
> 
> Normal Output:
> $ bridge -d -s mdb show
> dev br0 port swp3 grp 239.0.0.1 temp  vid 128 172.26
> dev br0 port swp3 grp 239.0.0.1 temp  vid 64 172.26
> dev br0 port swp2 grp 239.0.0.2 temp  vid 1024 172.26
> dev br0 port swp2 grp 239.0.0.2 temp  vid 256 172.26
> dev br0 port swp2 grp 239.0.0.2 temp  vid 1 172.26
> dev br0 port swp3 grp 239.0.0.1 temp  vid 1 172.26
> router ports on br0: swp4    0.00 permanent
> router ports on br0: swp5    0.00 permanent
> 
> Json Output:
> $ bridge -d -s -j mdb show
> {
>     "mdb": [{
>             "dev": "br0",
>             "port": "swp3",
>             "grp": "239.0.0.1",
>             "state": "temp",
>             "vid": 128,
>             "timer": " 166.74"
>         },{
>             "dev": "br0",
>             "port": "swp3",
>             "grp": "239.0.0.1",
>             "state": "temp",
>             "vid": 64,
>             "timer": " 166.74"
>         },{
>             "dev": "br0",
>             "port": "swp2",
>             "grp": "239.0.0.2",
>             "state": "temp",
>             "vid": 1024,
>             "timer": " 166.74"
>         },{
>             "dev": "br0",
>             "port": "swp2",
>             "grp": "239.0.0.2",
>             "state": "temp",
>             "vid": 256,
>             "timer": " 166.74"
>         },{
>             "dev": "br0",
>             "port": "swp2",
>             "grp": "239.0.0.2",
>             "state": "temp",
>             "vid": 1,
>             "timer": " 166.74"
>         },{
>             "dev": "br0",
>             "port": "swp3",
>             "grp": "239.0.0.1",
>             "state": "temp",
>             "vid": 1,
>             "timer": " 166.74"
>         }
>     ],
>     "router": {
>         "br0": [{
>                 "port": "swp4",
>                 "timer": "   0.00",
>                 "type": "permanent"
>             },{
>                 "port": "swp5",
>                 "timer": "   0.00",
>                 "type": "permanent"
>             }
>         ]
>     }
> }
> 
> Signed-off-by: Nikhil Gajendrakumar <nikhil@cumulusnetworks.com>
> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>

Applied, you should also update usage message and man page.

  reply	other threads:[~2017-07-19  0:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-07 22:24 [PATCH iproute2 net-next] bridge: this patch adds json support for bridge mdb show Roopa Prabhu
2017-07-19  0:33 ` Stephen Hemminger [this message]
2017-07-24 22:29   ` Nikhil Gajendrakumar

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=20170718173351.55cb566a@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.org \
    --cc=nikhil@cumulusnetworks.com \
    --cc=nikolay@cumulusnetworks.com \
    --cc=roopa@cumulusnetworks.com \
    /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).