netdev - Re: [PATCH iproute2 net-next v4 0/5] bridge: json support for fdb and vlan show

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: <CAJieiUjUy-uhw=fONKvsnaHEu_8WcLiJhBL30Aze8F4_-d2gww@mail.gmail.com>
Date:	Thu, 23 Jun 2016 04:03:28 -0700
From:	Roopa Prabhu <roopa@...ulusnetworks.com>
To:	Jiri Pirko <jiri@...nulli.us>
Cc:	Stephen Hemminger <stephen@...workplumber.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Anuradha Karuppiah <anuradhak@...ulusnetworks.com>,
	Nikolay Aleksandrov <nikolay@...ulusnetworks.com>,
	Julien Fortin <julien@...ulusnetworks.com>
Subject: Re: [PATCH iproute2 net-next v4 0/5] bridge: json support for fdb and
 vlan show

On Wed, Jun 22, 2016 at 1:00 PM, Jiri Pirko <jiri@...nulli.us> wrote:
> Wed, Jun 22, 2016 at 08:10:47PM CEST, stephen@...workplumber.org wrote:
>>On Wed, 22 Jun 2016 16:53:44 +0200
>>Jiri Pirko <jiri@...nulli.us> wrote:
>>
>>> Wed, Jun 22, 2016 at 03:45:50PM CEST, roopa@...ulusnetworks.com wrote:
>>> >From: Roopa Prabhu <roopa@...ulusnetworks.com>
>>> >
>>> >This patch series adds json support for a few bridge show commands.
>>> >We plan to follow up with json support for additional commands soon.
>>>
>>> I'm just curious, what is you use case for this? Apps can use rtnetlink
>>> socket directly.
>>
>>Try using netlink in perl or python, it is quite difficult.
>
> pyroute2? Quite easy...

none of the implementations out there are complete nor can compete
with iproute2.
iproute2 is maintained by netdev community and always is up-todate
with the latest
networking api.

Nothing against pyroute2 but we wrote our own for other reasons and we
carry additional burden of maintaining it and keeping it up-todate for
every networking api..
that gets added to iproute2 (and the implementation of netlink
is often very easy in C).

Also, for external automation and orchestration tools (to whom this
patch-set is addressed),
there is no reason for them to write and maintain their own tools
using netlink when they
can use iproute2 directly to create a link or query its properties.