netdev - Re: PATCH WAS( Re: [ANNOUNCE] iproute2 v2.6.25

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]

Date:	Mon, 21 Apr 2008 15:39:56 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	hadi@...erus.ca
CC:	Stephen Hemminger <shemminger@...tta.com>, netdev@...r.kernel.org,
	Thomas Graf <tgraf@...g.ch>
Subject: Re: PATCH WAS( Re: [ANNOUNCE] iproute2 v2.6.25

jamal wrote:
> On Mon, 2008-21-04 at 13:50 +0200, Patrick McHardy wrote:
> 
> 
>> I just noticed the libnl example code already supports this:
>>
>> $ ./nl-link-dump env dev eth0
>> LINK_NAME=eth0
>> LINK_IFINDEX=2
>> LINK_FAMILY=unspec
>> LINK_TYPE=ether
>> ...
>>
>> I wouldn't duplicate it for iproute, but rather complete the
>> libnl support (I think some object types are still missing
>> ENV dump format support) and tell people to use that for
>> scripting.
> 
> Sounds sensible.
> It would be useful to probably port iproute2 to use libnl. Or something
> new that provides iproute2 input/output.


Yes, that would be nice, the iproute netlink infrastructure is really
lagging behind. I'm not sure which way would be preferrable, build
something new on top of libnl without disturbing existing users or
gradually port iproute on top of libnl, probably starting with the
netlink infrastructure.

> on libnl (CC Thomas):
> I havent looked at libnl in a long time; it is certainly the right
> direction forward - my main contention with it (which i mentioned to
> Thomas) is it has too many knobs/hooks. Last conversation we had he told
> me it is optional for me to use all those knobs. For a geek that may not
> be sufficient answer: if you give me a swiss army knife i need to know
> what everything does ;->
 >
> Once you go that path network code that provides callbacks in more than
> send/recv as well as statefulness (like caching runtime objects which
> libnl did when i looked) then you no longer pass the smell-test for
> "library" - you are into "framework" domain[1] - which requires more
> steep knowledge of the framework to bypass mechanisms provided to you
> that you dont like. I tried to port some app back then from libnetlink
> to libnl and found it to be extra curve-climbing and abandoned it; i
> will revisit at some point.

Yes, its a bit overwhelming at the beginning because of all
those knobs, but the simple things are actually real easy :)

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html