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] [day] [month] [year] [list]
Message-Id: <7823F297-DB01-4C57-A8B8-296700A1184D@cumulusnetworks.com>
Date:   Mon, 24 Jul 2017 15:29:18 -0700
From:   Nikhil Gajendrakumar <nikhil@...ulusnetworks.com>
To:     Stephen Hemminger <stephen@...workplumber.org>
Cc:     Roopa Prabhu <roopa@...ulusnetworks.com>, netdev@...r.kernel.org,
        nikolay@...ulusnetworks.com
Subject: Re: [PATCH iproute2 net-next] bridge: this patch adds json support
 for bridge mdb show

Hello Stephen, 

Thanks you.
I will send an incremental patch with updated usage message and man page.

-Nikhil

> On Jul 18, 2017, at 5:33 PM, Stephen Hemminger <stephen@...workplumber.org> wrote:
> 
> On Fri,  7 Jul 2017 15:24:16 -0700
> Roopa Prabhu <roopa@...ulusnetworks.com> wrote:
> 
>> From: Nikhil Gajendrakumar <nikhil@...ulusnetworks.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@...ulusnetworks.com>
>> Signed-off-by: Roopa Prabhu <roopa@...ulusnetworks.com>
> 
> Applied, you should also update usage message and man page.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ