netdev - Re: iproute2 and libnl3?

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>] [day] [month] [year] [list]

Message-ID: <20130923121952.47ba4d66@nehalam.linuxnetplumber.net>
Date:	Mon, 23 Sep 2013 12:19:52 -0700
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	Arvid Brodin <arvid.brodin@...n.com>
Cc:	netdev@...r.kernel.org
Subject: Re: iproute2 and libnl3?

On Mon, 23 Sep 2013 11:17:40 -0700
Arvid Brodin <arvid.brodin@...n.com> wrote:

> Hi Stephen (and others),
> 
> I'm trying to move the functionality from a small user space tool I wrote for 
> listening to HSR Netlink messages into iproute2. The tool uses generic netlink 
> through libnl3. 
> 
> It seems iproute2 uses libnl-1 though:
> 
> iphsr.c:325:6: warning: 'struct nl_sock' declared inside parameter list
> iphsr.c:334:30: error: 'NL_AUTO_PORT' undeclared (first use in this function)
> iphsr.c:341:2: warning: implicit declaration of function 'nl_send_auto'
> iphsr.c:417:2: warning: implicit declaration of function 'genl_ctrl_resolve_grp'
> iphsr.c:424:2: warning: implicit declaration of function 'nl_socket_add_memberships'
> iphsr.c:455:2: warning: implicit declaration of function 'nl_socket_alloc'
> iphsr.c:463:2: warning: implicit declaration of function 'nl_socket_disable_seq_check'
> 
> Are there alternatives to the above functionality in libnl-1, or do I need to 
> implement it myself (copy them from the libnl3 code perhaps)?
> 
> 

Upstream version of iproute does not use libnl.
Any patches to use libnl are rejected. iproute2 has its own internal libnetlink  library.

--
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