From: Duncan Roe <duncan_roe@optusnet.com.au>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Development <netfilter-devel@vger.kernel.org>
Subject: Convert libnetfilter_queue to not need libnfnetlink
Date: Wed, 27 Mar 2024 09:06:43 +1100 [thread overview]
Message-ID: <ZgNG88d1sAkgl+BU@slk15.local.net> (raw)
Hi Pablo,
On Mon, Sep 11, 2023 at 09:51:07AM +0200, Pablo Neira Ayuso wrote:
> On Mon, Sep 11, 2023 at 03:54:25PM +1000, Duncan Roe wrote:
[SNIP]
> > libnetfilter_queue effectively supports 2 ABIs, the older being based on
> > libnfnetlink and the newer on libmnl.
>
> Yes, there are two APIs, same thing occurs in other existing
> libnetfilter_* libraries, each of these APIs are based on libnfnetlink
> and libmnl respectively.
>
[SNIP]
>
> libnfnetlink will go away sooner or later. We are steadily replacing
> all client of this library for netfilter.org projects. Telling that
> this is not deprecated without providing a compatible "old API" for
> libmnl adds more confusion to this subject.
>
> If you want to explore providing a patch that makes the
> libnfnetlink-based API work over libmnl, then go for it.
OK I went for it. But I posted the resultant patchset as a reply to an
earlier email.
The Patchwork series is
https://patchwork.ozlabs.org/project/netfilter-devel/list/?series=399143
("Convert nfq_open() to use libmnl").
The series is "code only" - I kept back the documentation changes for
spearate review. These documentation changes present the "old API" as
merely an alternative to the mnl API: both use libmnl.
Do you think you might find time to look at it before too long? I know you
are very busy but I would appreciate some feedback.
Cheers ... Duncan.
reply other threads:[~2024-03-26 22:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZgNG88d1sAkgl+BU@slk15.local.net \
--to=duncan_roe@optusnet.com.au \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).