netdev - Re: yaml gen NL families support in iproute2?

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: <20241029063939.244e2c67@kernel.org>
Date: Tue, 29 Oct 2024 06:39:39 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Paolo Abeni <pabeni@...hat.com>
Cc: Joe Damato <jdamato@...tly.com>, David Ahern <dsahern@...nel.org>,
 Stephen Hemminger <stephen@...workplumber.org>, "netdev@...r.kernel.org"
 <netdev@...r.kernel.org>
Subject: Re: yaml gen NL families support in iproute2?

On Tue, 29 Oct 2024 10:29:15 +0100 Paolo Abeni wrote:
> > That's assuming that by
> > 
> >   so that end-users/admins could consolidated administration/setup 
> >   in a single tool
> > 
> > you mean that you are aiming to create a single tool capable of
> > handling arbitrary specs. > If you want to make the output
> > and input more "pretty" than just attrs in / attrs out -- then
> > indeed building on top of libynl.a makes sense.  
> 
> My understanding is that a similar/consistent command line and man page
> based documentation will preferable for the end-user - say to configure
> ip addresses and configure tx shaping on a given device.

I see. You got me slightly confused with "single tool" as iproute2
itself contains multiple tools. Sounds like you just want to write
a tool / add to ip the ability to talk net shaper nl.