Fabien C. <7o5fzvj4duxjxzp@xxxxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
