From: Pablo Neira Ayuso <pablo@netfilter.org>
To: William Blough <devel@blough.us>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH libnetfilter_conntrack 1/1] conntrack: Allow setting of netlink buffer size
Date: Wed, 11 Jan 2023 18:27:21 +0100 [thread overview]
Message-ID: <Y77xebdD+v9ZjEyb@salvia> (raw)
In-Reply-To: <Y7h1o0H+dvAz1vtZ@prometheus>
On Fri, Jan 06, 2023 at 02:25:23PM -0500, William Blough wrote:
> ENOBUFS is returned in the case that the nfnetlink socket buffer is
> exhausted. The function nfnl_rcvbufsize is provided by libnfnetlink
> to set the buffer size in order to handle this error, however
> libnetfilter_conntrack does not expose this function for the underlying
> netlink socket.
>
> Add nfct_rcvbufsiz function to allow setting of buffer size for netlink
> socket.
Thanks for your patch.
There is already nfct_fd() and you can use setsockopt() on it.
next prev parent reply other threads:[~2023-01-11 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 19:25 [PATCH libnetfilter_conntrack 1/1] conntrack: Allow setting of netlink buffer size William Blough
2023-01-11 17:27 ` Pablo Neira Ayuso [this message]
2023-01-11 18:20 ` Bill Blough
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=Y77xebdD+v9ZjEyb@salvia \
--to=pablo@netfilter.org \
--cc=devel@blough.us \
--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 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 NNTP newsgroup(s).