Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Alessandro Vesely <vesely@tana.it>
Cc: netfilter@vger.kernel.org
Subject: Re: nfnetlink: This library is not meant as a public API for application developers.
Date: Thu, 13 Feb 2020 14:55:04 +0100	[thread overview]
Message-ID: <20200213135504.srhuuph4sd7pd7ne@salvia> (raw)
In-Reply-To: <bcff17cd-1457-7454-e00f-22d798afd7e5@tana.it>

Hi,

On Thu, Feb 13, 2020 at 12:27:41PM +0100, Alessandro Vesely wrote:
> Has that disclaimer always been in libnfnetlink home page[*]?
> 
> It is the first time I see it.
>
> I have a userspace filter[†] working with it, and it currently works well.
> 
> If I remove -lnfnetlink from the link command, I get just one undefined
> reference to symbol 'nfnl_rcvbufsiz'.  It is used only if there is a command
> line option to set the buffer size to a given size, to avoid enobufs.  For the
> rest, the daemon uses libnetfilter_queue.
> 
> Should I rewrite that?  How?

Probably, we should rewrite that sentence to: "For new software,
please consider using libmnl instead." which is actually the
intention.

libnetfilter_queue also provides an API that combines well with
libmnl.

There is no plans to remove libnfnetlink anytime soon, it's still
being used by netfilter userspace software.

  reply	other threads:[~2020-02-13 13:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 11:27 nfnetlink: This library is not meant as a public API for application developers Alessandro Vesely
2020-02-13 13:55 ` Pablo Neira Ayuso [this message]
2020-04-12  8:21 ` Duncan Roe
2020-04-13 18:46   ` Alessandro Vesely
2020-04-22  1:37     ` 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=20200213135504.srhuuph4sd7pd7ne@salvia \
    --to=pablo@netfilter.org \
    --cc=netfilter@vger.kernel.org \
    --cc=vesely@tana.it \
    /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