All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Павел Коколемин" <pavelkok@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: nfnl_listen: recvmsg overrun: No buffer space available" in	nfct_event_conntrack() call
Date: Thu, 01 Feb 2007 14:56:37 +0100	[thread overview]
Message-ID: <45C1F195.50006@netfilter.org> (raw)
In-Reply-To: <45C1ABA7.80600@netfilter.org>

Pablo Neira Ayuso wrote:
> Павел Коколемин wrote:
>> When LAN users start network scanners (NetLook, for example),
>> sometimes I receive error in console:
>> "nfnl_listen: recvmsg overrun: No buffer space available"
>> generated in nfct_event_conntrack() (recvmsg() returns ENOBUFS error 
>> code).
>> This message generated in nfnl_listen().
> 
> Increase netlink buffer size via nfnl_rcvsiz() (libnfnetlink), the 
> default size is available in /proc/sys/net/core/rmem_max. BTW, this 
> message means that you have probably lost some log messages because the 
> rate was so high that the buffer could not back off.

Sorry, I didn't notice that there is no way to access nfnl_handle from 
libnetfilter_conntrack, instead use setsockopt(nfct_fd(h), SOL_SOCKET, 
SO_RCVBUFFORCE, &size, socklen) to set the buffer size. Anyway I'll cook 
a patch for this asap, this issue is important.

-- 
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


  reply	other threads:[~2007-02-01 13:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-31 22:31 nfnl_listen: recvmsg overrun: No buffer space available" in nfct_event_conntrack() call Павел Коколемин
2007-02-01  8:58 ` Pablo Neira Ayuso
2007-02-01 13:56   ` Pablo Neira Ayuso [this message]
2007-02-01 17:31     ` Павел Коколемин

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=45C1F195.50006@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=netfilter@lists.netfilter.org \
    --cc=pavelkok@gmail.com \
    /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.