From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter@vger.kernel.org
Subject: Re: Extending an IPv4 filter to IPv6
Date: Sun, 20 Aug 2023 23:39:55 +0200 [thread overview]
Message-ID: <ZOKIK0P6voN9dBS3@calendula> (raw)
In-Reply-To: <ZOAe3rziTGTkTyfi@slk15.local.net>
On Sat, Aug 19, 2023 at 11:46:06AM +1000, Duncan Roe wrote:
> On Fri, Aug 18, 2023 at 12:56:38PM +0200, Alessandro Vesely wrote:
[...]
> There are 2 separate APIs in libnetfilter_queue, examplified by
> utils/nfqnl_test.c (your program) and examples/nf-queue.c (newer, has functions
> for packet mangling).
>
> DEPRECATED was an unfortunate choice of label for the older API: the functions
> are not deprecated but the underlying library that they currently use is
> deprecated. In answer to your questions:
>
> 1a Can I keep using these functions?: Certainly.
No. For new applications, the new libmnl-based API is the way to go.
Old API depends on libnfnetlink and it will go away sooner or later if
there is not a way to make it work behind the scenes with libmnl.
We are steadly removing all users of libnfnetlink in favour of libmnl.
next prev parent reply other threads:[~2023-08-20 21:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 10:56 Extending an IPv4 filter to IPv6, Extending an IPv4 filter to IPv6 Alessandro Vesely
2023-08-19 1:46 ` Duncan Roe
2023-08-19 9:53 ` Extending an IPv4 filter to IPv6, " Alessandro Vesely
2023-08-20 1:09 ` Duncan Roe
2023-08-20 21:39 ` Pablo Neira Ayuso [this message]
2023-08-20 21:41 ` Pablo Neira Ayuso
2023-08-21 17:18 ` Extending an IPv4 filter to IPv6, " Alessandro Vesely
2023-08-21 19:10 ` Pablo Neira Ayuso
2023-08-22 18:09 ` Extending an IPv4 filter to IPv6, " Alessandro Vesely
2023-08-27 8:34 ` Duncan Roe
2023-08-27 17:20 ` Extending an IPv4 filter to IPv6, " Alessandro Vesely
2023-08-27 18:58 ` Duncan Roe
2023-08-27 21:12 ` Pablo Neira Ayuso
2023-08-27 20:49 ` Pablo Neira Ayuso
2023-08-27 20:48 ` Pablo Neira Ayuso
2023-08-31 9:22 ` Extending an IPv4 filter to IPv6, " Alessandro Vesely
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=ZOKIK0P6voN9dBS3@calendula \
--to=pablo@netfilter.org \
--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.