From: Eric Leblond <eric@inl.fr>
To: ryan.vanriper@adventiumlabs.org
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ENOBUF error during recv
Date: Fri, 09 Jan 2009 23:09:25 +0100 [thread overview]
Message-ID: <1231538965.30864.6.camel@ice-age> (raw)
In-Reply-To: <200901091454.45485.ryan.vanriper@adventiumlabs.org>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
Hi,
Le vendredi 09 janvier 2009 à 14:54 -0600, Ryan VanRiper a écrit :
> I am using the nfqnl_test.c program and noticed that under network load (ie.
> sending a 20meg text file) the while loop doing the recv in main() fails and
> after some debugging returns a perror of ENOBUFF (105) ?
>
> Any ideas why this would happen ?
>
> I using centos 5.2 i386 32bit, and 2.6.18 kernel.
This question has been answer during the last 15 days, please check the
archive before asking:
http://marc.info/?l=netfilter-devel&m=123099679021495&w=2
The nfnetlink buffer is full. For production system, you can increase it
with
nfnl_rcvbufsiz(nfq_nfnlh(h), SIZE);
BR,
--
Eric Leblond <eric@inl.fr>
INL: http://www.inl.fr/
NuFW: http://www.nufw.org/
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-01-09 22:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 2:13 doc: escape minus sign in manpages Jan Engelhardt
2009-01-09 20:54 ` ENOBUF error during recv Ryan VanRiper
2009-01-09 22:09 ` Eric Leblond [this message]
2009-01-12 1:36 ` doc: escape minus sign in manpages Pablo Neira Ayuso
2009-01-12 2:39 ` Jan Engelhardt
2009-01-12 3:53 ` Patrick McHardy
2009-01-12 6:07 ` Jan Engelhardt
2009-01-12 6:20 ` Patrick McHardy
2009-01-14 5:47 ` Jan Engelhardt
2009-01-16 8:05 ` Patrick McHardy
2009-01-16 8:19 ` Jan Engelhardt
2009-01-19 14:35 ` Patrick McHardy
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=1231538965.30864.6.camel@ice-age \
--to=eric@inl.fr \
--cc=netfilter-devel@vger.kernel.org \
--cc=ryan.vanriper@adventiumlabs.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).