From: Stephen Hemminger <stephen@networkplumber.org>
To: Arvid Brodin <arvid.brodin@xdin.com>
Cc: netdev@vger.kernel.org
Subject: Re: iproute2 and libnl3?
Date: Mon, 23 Sep 2013 12:19:52 -0700 [thread overview]
Message-ID: <20130923121952.47ba4d66@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1902752B0C92F943AB7EA9EE13E2DEEC1272C74D80@HQ1-EXCH02.corp.brocade.com>
On Mon, 23 Sep 2013 11:17:40 -0700
Arvid Brodin <arvid.brodin@xdin.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.
next parent reply other threads:[~2013-09-23 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1902752B0C92F943AB7EA9EE13E2DEEC1272C74D80@HQ1-EXCH02.corp.brocade.com>
2013-09-23 19:19 ` Stephen Hemminger [this message]
2013-09-23 18:17 iproute2 and libnl3? Arvid Brodin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130923121952.47ba4d66@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=arvid.brodin@xdin.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox