From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>,
Netfilter Development <netfilter-devel@vger.kernel.org>
Subject: Re: Request for comments
Date: Mon, 2 Sep 2024 14:33:01 +0200 [thread overview]
Message-ID: <ZtWwfYTF1TC8UMh_@calendula> (raw)
In-Reply-To: <ZtVPczkT/T9Zz0ep@slk15.local.net>
Hi Duncan,
On Mon, Sep 02, 2024 at 03:38:59PM +1000, Duncan Roe wrote:
> Hi Florian,
>
> Recently I submitted patch series
> https://patchwork.ozlabs.org/project/netfilter-devel/list/?series=407990 which
> converts libnetfilter_queue to not need libnfnetlink.
>
> The series re-implements all the libnfnetlink-wrapper functions so they use
> functions from libmnl. I understand from previous correspondence that you had a
> shot at doing the same thing a while back. With that in mind, would you be able
> to find the time to take a look at the series and comment on it?
>
> Additionally, the series re-implements the nlif_* functions from libnfnetlink.
> conntrack-tools and ulogd also use these functions, so I wonder if they belong
> in libmnl. Would you have an opinion on that?
>
> Please disregard my use of kernel headers - I now understand the idea of cached
> headers is to be able to do standalone builds without them. v3 would fix that.
I have huge concerns this will break existing applications for the
benefit of nothing? Because other existing libraries rely on
libnfnetlink.
Unless he finds a way to carefully sends us patches to incrementally
move to libmnl.
I think it is more sensible to extend the new API to fill the missing
gaps, I remember people mentioned it is too low level. With a few
helper function it should be possible to make it as easy to use for
simple applications a libnetfilter_queue.
next prev parent reply other threads:[~2024-09-02 12:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 5:38 Request for comments Duncan Roe
2024-09-02 12:33 ` Pablo Neira Ayuso [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-10 16:22 Barclay Jameson
2014-10-10 17:04 ` John Spray
2002-12-06 18:33 Request for Comments Jan Willem Stumpel
[not found] <Pine.LNX.4.21.0107191757400.17990-100000@groove.rdsnet.ro.suse.lists.linux.kernel>
2001-07-19 17:33 ` Request for comments Andi Kleen
2001-07-19 17:52 ` Jakob Østergaard
2001-07-19 15:44 Cornel Ciocirlan
2001-07-19 16:30 ` Crutcher Dunnavant
2001-07-19 17:24 ` Francois Romieu
2001-07-19 17:29 ` jlnance
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=ZtWwfYTF1TC8UMh_@calendula \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@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.