From: Pablo Neira Ayuso <pablo@netfilter.org>
To: fabien.marotte@mindspeed.com
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: libnetfilter_conntrack, nfct_catch returns ENOBUFS
Date: Mon, 18 Jun 2007 18:10:18 +0200 [thread overview]
Message-ID: <4676AE6A.7060605@netfilter.org> (raw)
In-Reply-To: <OF4720118A.9A817D9F-ONC12572FE.0056ADED-C12572FE.0056CBFD@mindspeed.com>
fabien.marotte@mindspeed.com wrote:
> I develop an application using libnetfilter_conntrack to catch events
> happening in the conntrack system.
> I am currently testing the robustness of my application using ab tool
> (connection stress).
>
> libnetfilter_conntrack version is 0.50. I use the new API.
> My callback catching the events always returns NFCT_CB_CONTINUE meaning
> that ncft_catch should never returns.
>
> But with 20 (and more) TCP connections opening simultaneously, nfct_catch
> returns. The error code in errno is 105. Seems to be ENOBUFS.
>
> Looking at the code, I see the comment "ENOBUFS is returned in case that
> nfnetlink is exhausted".
>
> I am very surprised to have memory issues with so few connections.
So am I. Could you post the code?
> Could you explain me why this error occurs ? Is this a kernel error
> propagated in user space or is this a user space error ?
Default buffer size in your system? cat /proc/sys/net/core/rmem_default
--
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris
next prev parent reply other threads:[~2007-06-18 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 15:47 libnetfilter_conntrack, nfct_catch returns ENOBUFS fabien.marotte
2007-06-18 16:10 ` Pablo Neira Ayuso [this message]
2007-06-18 16:56 ` fabien.marotte
2007-06-18 18:11 ` Pablo Neira Ayuso
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=4676AE6A.7060605@netfilter.org \
--to=pablo@netfilter.org \
--cc=fabien.marotte@mindspeed.com \
--cc=netfilter-devel@lists.netfilter.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.