From: Florian Westphal <fw@strlen.de>
To: "Fabien C." <7o5fzvj4duxjxzp@jetable.org>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Subject: Re: libnetfilter_queue: Some accepted packets get lost
Date: Thu, 10 Mar 2011 07:29:22 +0100 [thread overview]
Message-ID: <20110310062922.GY8821@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <4D780CD3.2000006@jetable.org>
Fabien C. <7o5fzvj4duxjxzp@jetable.org> wrote:
> Hello Pablo,
>
> >> 01) 20:08:00.486366: recv returned 108
> >> 02) 20:08:00.486566: setting verdict : accept the packet...
> >> 03) 20:08:00.486614 IP 10.3.5.8.46938 > 10.3.5.1.53: 51146+ A? www.mydomain.net. (35)
> >> 04) 20:08:00.487193 IP 10.3.5.1.53 > 10.3.5.8.46938: 51146 1/3/3 A 12.34.123.210 (157)
> >> 05) 20:08:00.586723: recv returned 108
> >> 06) 20:08:00.586789: setting verdict : accept the packet...
> >> [==> tcpdump doesn't see this one - so browser waits for 5sec, and retries]
> >
> > Check for errors in recv() to see if you are hitting ENOBUFS.
>
> Nope. recv() seems to be fine. As you can see from the output I gave in my
> first message, it always returns positive values "recv returned 108".
>
> For the record, I must add: I compiled a custom 2.6.32 and surprisingly still
> have the problem. Is it my config, or the Debian patches that make the
> difference, I don't know...
perhaps you're hitting this problem?:
http://marc.info/?l=netfilter-devel&m=129016166319433&w=2
It triggers when your receive a 2nd UDP packet with the same
address/port pair while the 1st packet is still queued.
next prev parent reply other threads:[~2011-03-10 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 23:04 libnetfilter_queue: Some accepted packets get lost Fabien C.
2011-03-09 13:44 ` Pablo Neira Ayuso
2011-03-09 23:27 ` Fabien C.
2011-03-10 6:29 ` Florian Westphal [this message]
2011-03-10 13:51 ` Pablo Neira Ayuso
2011-03-10 21:21 ` Fabien C.
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=20110310062922.GY8821@Chamillionaire.breakpoint.cc \
--to=fw@strlen.de \
--cc=7o5fzvj4duxjxzp@jetable.org \
--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 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).