Hello, If I use any kernel above 2.6.16 (2.6.17-1.2187_FC5smp for example), I cannot download this file (with wget for example) - http://www.itu.int/plenipotentiary/2006/structure/draft-tmp.doc . Download is very slow and timeouts, and with a sniffer I see a lot of packets with TCP segment of a reassembled PDU. If I boot 2.6.16-1.2122_FC5smp kernel, file is downloaded OK. It happens only on some PCs, usually when they are connected to DSL.
The same or similar problem is with projects.ivija.com - for example, links https://projects.ivija.com/ timeouts. But it works if I boot 2.6.16-1.2133_FC5 kernel.
What does 'ifconfig <eth> device' tell you for the MTU on each kernel?
Please include the output of running "sysreport"...thanks!
MTU:1500. I tried changing (lowering) it, didn't help.
sysreport output file was quite large. But I don't think you need it - it happens on about 5 different PCs in different locations - both 32 and 64 bit, different network cards (e100 and 3c59x), both new FC5 installations and systems upgraded from earlier Fedora versions. SELinux is disabled. What matters is internet connection (equipment - routers etc) - it works on my home PC, which is connected to 10 mbps LAN, and doesn't work on servers connected to ADSL or T1.
Nerijus, There was a change in the 2.6.17 and later kernels to the TCP stack that resulted in the problem that TCP packets wouldn't go through certain routers - which is exactly what you are hitting. I did see a fix, but I can't recall where and when I saw it - searching my e-mail archives did not yield anything either. John, who this bug is assigned to, would probably have a better idea.
kernel-2.6.18-1.2200.fc5.i686 still has this problem.
Konrad, comment 7 doesn't "ring any bells" for me. Comment 8 would seem to indicate that this is another issue. Nerijus, please attach the information I requested in comment 4. I'm sorry, but "works on my home PC...doesn't work on servers connected to ADSL or T1" and "lot of packets with TCP segment of a reassembled PDU" just isn't enough information.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.
Why another issue? Konrad said "There was a change in the 2.6.17 and later kernels...", so it doesn't mean it is fixed in 2.6.18. He "did see a fix, but I can't recall where and when" - so I assume the fix was not applied to 2.6.18, and as I already told, the problem still exists in 2.6.18-1.2200.fc5. I can't attach sysreport output, as tar file was more than 500 MB, and I canceled bzip2'ing after few minutes. I think bz2 file will be too big to attach here. I know it isn't enough information, but I believe it's "There was a change in the 2.6.17 and later kernels to the TCP stack that resulted in the problem that TCP packets wouldn't go through certain routers - which is exactly what you are hitting". So either you can reproduce it or send me a fix which I can try (I'll try to find it in linux-kernel list archives).
John, I think Konrad was referring to the window scaling changes that happened circa 2.6.17
Thanks for the tip, Dave... Nerijus, you might try doing this (as root) before connecting to the sites in question: echo 0 > /proc/sys/net/ipv4/tcp_window_scaling For a slightly less "ham-handed" approach, you could try this: echo 4096 87380 174760 > /proc/sys/net/ipv4/tcp_rmem Please try those (at least the first one) and post the results here...thanks! P.S. Links of interest: http://marc.theaimsgroup.com/?l=linux-netdev&m=114478312100641&w=2> http://kerneltrap.org/node/6723 http://lwn.net/Articles/92727/ (old, but decent background info)
*** Bug 209630 has been marked as a duplicate of this bug. ***
John, both workarounds worked, thanks (I tried them on different servers). Should I use one of them or will updated kernel be released?
It isn't a kernel bug. It's a sign of a broken router between you and the target host that can't do window scaling correctly.
It is probably worth to add info about this problem to FC6 release notes.
Dave amd John, Thanks for coming to rescue.
*** Bug 216815 has been marked as a duplicate of this bug. ***
*** Bug 217063 has been marked as a duplicate of this bug. ***
*** Bug 219483 has been marked as a duplicate of this bug. ***
Oke this work-around does work oke. But saying it's the routers fault it's a little bit to easy imho. Previous versions in the FC 5 kernels didn't have the problems. Oh well the workaround works well enough :)