From: Anton <anton.vazir@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: (nfnl_talk: recvmsg over-run) and (nf_queue: full at 1024 entries, dropping packets(s). Dropped: 582) - bug or just some defaults increase required?
Date: Mon, 9 Feb 2009 15:56:24 +0500 [thread overview]
Message-ID: <200902091556.25407.anton.vazir@gmail.com> (raw)
In-Reply-To: <498E3693.6030702@netfilter.org>
Pablo,
Just a little more thought, this happened when my
application attempted to create a NEW queue, while in
kernel packet queue overrun situation. And after calling
the nfq_create_queue there was no return from it, and only
error message generation in the loop inside the
libnetfilter_queue library. Looks like not a very proper
behaviour. Am I missing something?
With best regards,
Anton.
On Sunday 08 February 2009 06:34, Pablo Neira Ayuso wrote:
> Anton VG wrote:
> > Hello Friends,
> >
> > Just came to a problem with nfnetlink_queue -
> >
> > I've created a service where users do connect to a
> > host, and every connected user (over PPP) get's a
> > separate NF-QUEUE - In this QUEUE i do packet
> > accounting, to a different destination. When number of
> > simultaneous queues went to 40+ I just came to a
> > problem - deadloop with continues generation of the
> > error to stderr - (3GB of record in the log in 3
> > minutes of deadlock)
> >
> > nfnl_talk: recvmsg over-run
>
> This happens when netlink fails to deliver a packet from
> kernel to userspace due to an overrun in the buffer.
>
next prev parent reply other threads:[~2009-02-09 11:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 18:14 (nfnl_talk: recvmsg over-run) and (nf_queue: full at 1024 entries, dropping packets(s). Dropped: 582) - bug or just some defaults increase required? Anton VG
2009-02-08 1:34 ` Pablo Neira Ayuso
2009-02-09 10:56 ` Anton [this message]
2009-02-09 11:20 ` Pablo Neira Ayuso
2009-02-11 8:48 ` Anton
[not found] ` <49928B62.1090600@netfilter.org>
2009-02-11 12:26 ` Anton VG
2009-02-11 16:41 ` Pablo Neira Ayuso
2009-02-12 10:45 ` Anton
2009-02-12 12:43 ` Pablo Neira Ayuso
2009-02-14 9:03 ` Anton
2009-02-14 17:13 ` Pablo Neira Ayuso
2009-02-16 13:19 ` Anton
2009-02-16 13:42 ` Pablo Neira Ayuso
2009-02-16 14:38 ` Anton VG
2009-02-16 15:23 ` Pablo Neira Ayuso
2009-02-16 15:33 ` Anton VG
2009-02-16 15:41 ` Anton VG
2009-02-17 16:58 ` Anton VG
2009-02-17 17:15 ` Pablo Neira Ayuso
2009-02-17 17:31 ` Anton VG
2009-02-18 2:48 ` Amos Jeffries
2009-02-17 17:34 ` Anton VG
2009-02-17 19:51 ` 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=200902091556.25407.anton.vazir@gmail.com \
--to=anton.vazir@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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.