From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Netfilter Development <netfilter-devel@vger.kernel.org>
Subject: Re: libnfnetlink dependency elimination (doc)
Date: Wed, 15 Nov 2023 12:46:49 +0100 [thread overview]
Message-ID: <ZVSvqR0cfw5zfVnd@calendula> (raw)
In-Reply-To: <ZVSu+NTsJKP6YgQ1@slk15.local.net>
On Wed, Nov 15, 2023 at 10:43:52PM +1100, Duncan Roe wrote:
> On Wed, Nov 15, 2023 at 10:27:34AM +0100, Pablo Neira Ayuso wrote:
> > On Wed, Nov 15, 2023 at 10:04:47AM +1100, Duncan Roe wrote:
> > > Hi Pablo,
> > >
> > > On Tue, Nov 14, 2023 at 04:24:11PM +0100, Pablo Neira Ayuso wrote:
> > > > On Sun, Nov 12, 2023 at 05:59:21PM +1100, Duncan Roe wrote:
> > > > > Some of these documented changes haven't happened yet.
> > > >
> > > > Then we have to start by changes first, not the other way around.
> > >
> > > Yes I know that, obviously:)
> > >
> > > The point here is that nfnl_rcvbufsiz() has been advertised in the main page of
> > > libnetfilter_queue HTML for a long time and there are likely a number of systems
> > > out there that use it. When libnfnetlink is removed, libnetfilter_queue will
> > > have to provide nfnl_rcvbufsiz() or those systems will start failing.
> >
> > There is nfq_fd() and setsockopt() that you can use:
> >
> > setsockopt(fd, SOL_SOCKET, SO_RCVBUFFORCE, &size, socklen);
> > setsockopt(fd, SOL_SOCKET, SO_RCVBUF, &size, socklen);
>
> Yes
> >
> > libnfnetlink is **deprecated** and it will be removed at some point,
> > the git log shows that it has less and less users.
>
> Good to know
> >
> > main libnfnetlink users are the libnetfilter_* libraries.
>
> Yes
> >
> > No new application should be using libnfnetlink in 2023.
>
> Yes
>
> But please see thread starting
> > [PATCH libnetfilter_queue] utils: Add example of setting socket buffer size
> I meant to send my reply to that email, not this one.
>
> Again sorry for the confusion I've caused.
Apologies, I got lost. Huge burden here.
I suggest to restart from scratch and only one submission and thread at a time :)
Thanks.
next prev parent reply other threads:[~2023-11-15 11:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 6:59 libnfnetlink dependency elimination Duncan Roe
2023-11-12 6:59 ` [PATCH libnetfilter_queue 1/1] doc: First update for libnfnetlink-based API over libmnl Duncan Roe
2023-11-14 15:24 ` libnfnetlink dependency elimination Pablo Neira Ayuso
2023-11-14 23:04 ` libnfnetlink dependency elimination (doc) Duncan Roe
2023-11-14 23:11 ` *** Scrub that last message Duncan Roe
2023-11-15 9:27 ` libnfnetlink dependency elimination (doc) Pablo Neira Ayuso
2023-11-15 11:43 ` Duncan Roe
2023-11-15 11:46 ` Pablo Neira Ayuso [this message]
2023-11-14 23:14 ` Duncan Roe
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=ZVSvqR0cfw5zfVnd@calendula \
--to=pablo@netfilter.org \
--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.