From: Eric Leblond <eric@inl.fr>
To: Jaco Kroon <jaco@uls.co.za>
Cc: netfilter@vger.kernel.org
Subject: Re: nlif_index2name bug?
Date: Sun, 18 Nov 2007 19:35:01 +0100 [thread overview]
Message-ID: <1195410901.6881.19.camel@localhost> (raw)
In-Reply-To: <473EE45F.8040008@uls.co.za>
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
Hi,
Le samedi 17 novembre 2007 à 14:53 +0200, Jaco Kroon a écrit :
> Hi guys,
>
> I've seen an error in nlif_index2name, specifically, if an interface
> comes up _after_ I've opened the nlif_handle (using nlif_open()) then it
> won't resolve the index of that device to a name.
>
> Is this a known issue, a bug or simply me not understanding how nlif
> works?
Yes, you did not understand how nlif is working (but I think this is due
to the lack of documentation). If fact, you have omit to listen to iface
events and to call nlif_catch after each event.
For a working code example, you can have a look at NuFW's code. nlif
related code is always prefixed by:
#ifdef HAVE_NLIF_CATCH
You can browse code online at:
http://software.inl.fr/trac/trac.cgi/browser/mirror/edenwall/nufw/trunk/nufw/src/nufw/packetsrv.c
http://software.inl.fr/trac/trac.cgi/browser/mirror/edenwall/nufw/trunk/nufw/src/nufw/iface.c
I've just wrote a brief nlif documentation on the following page:
http://software.inl.fr/trac/trac.cgi/wiki/articles/using_nlif
BR,
--
Eric Leblond <eric@inl.fr>
INL
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-11-18 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 12:53 nlif_index2name bug? Jaco Kroon
2007-11-18 18:35 ` Eric Leblond [this message]
2007-11-18 19:11 ` Jaco Kroon
2007-11-18 19:55 ` Jaco Kroon
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=1195410901.6881.19.camel@localhost \
--to=eric@inl.fr \
--cc=jaco@uls.co.za \
--cc=netfilter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.