You are not logged in.
good. did you guys tried this TCP_SACK thingie? it worked for me *shrug*
cheers Barde
Yup, seems to work
And yes, my router REALLY is crappy
Last edited by Theomachos (2008-10-17 11:47:58)
There is one thing even more vital to science than intelligent methods; and that is, the sincere desire to find out the truth, whatever it may be.
Charles S. Peirce
Offline
How do you apply the TCP_SACK thingie?
I can give it a try & see if it works with the upgraded kernel & associated files.
I have a Siemens Speedstream 4200, which doesn't have a great reputation as a modem/router.
I used to be surprised that I was still surprised by my own stupidity, finding it strangely refreshing.
Well, now I don't find it refreshing.
I'm over it!
Offline
I did have the same problems, could not connect to websites with firefox, use thunderbird or instant messaging. Downgrading dhcpcd didn't work, downgrading kernel26 and nvidia to the previous version worked! Trying the fix tomorrow, it's late now.
Offline
How do you apply the TCP_SACK thingie?
See this post.
BTW the tcp_sack fix does not work for me.
Offline
handy wrote:How do you apply the TCP_SACK thingie?
See this post.
BTW the tcp_sack fix does not work for me.
damn. that would have been a good workaround to post to the kernel mailing list because it actually points at some specific subsystem...
cheers barde
Offline
I just created an account at Bugzilla, & searched for kernel bugs open on: network, tcp tcpip dhcpcd & there are none.
I am a Linux kernel distro' beginner, so I have not posted this bug at Bugzilla.
Someone who knows what they are talking about more than I do should be the one to post this bug.
Please could someone spend 10 minutes or so & do it, someone?
I used to be surprised that I was still surprised by my own stupidity, finding it strangely refreshing.
Well, now I don't find it refreshing.
I'm over it!
Offline
Allright, now this is strange.
I applied the patch and most webpages work now, but only most. Anything with an encrypted connection does not load (except my banks website).
Imap is not working. Instant messaging can't connect to server.
I'm downgrading again.
Offline
Allright, now this is strange.
I applied the patch and most webpages work now, but only most. Anything with an encrypted connection does not load (except my banks website).
Imap is not working. Instant messaging can't connect to server.I'm downgrading again.
could you please be a little more specific. which don't load exactly? it's not easy to track down a bug when ppl simply say "it does not work" or "it does work now, somehow"
thank you
cheers Barde
Offline
handy wrote:How do you apply the TCP_SACK thingie?
See this post.
BTW the tcp_sack fix does not work for me.
the tcp_sack fix didn't work for me either. I am at a loss of where to find the previous kernel so i can downgrade, as i had recently done a pacman -Scc. I would, i guess, also need the previous nvidia and dhcpcd, as those seem to be dependent on it?
Last edited by opeth115 (2008-10-19 14:50:15)
Offline
I've been having this problem ever since the latest kernel appeared in the repositories. The only way around it I've found is to downgrade my kernel each time.
Offline
kiepmad wrote:Allright, now this is strange.
I applied the patch and most webpages work now, but only most. Anything with an encrypted connection does not load (except my banks website).
Imap is not working. Instant messaging can't connect to server.I'm downgrading again.
could you please be a little more specific. which don't load exactly? it's not easy to track down a bug when ppl simply say "it does not work" or "it does work now, somehow"
thank youcheers Barde
Ok, let's put it this way:
After applying TCP_SACK thingie, every website worked, except EVERY websites with https:// in their URL. However, there is ONE exception which is https://bcee.snet.lu. https//owa.uni.lu, my rootserver's webadmin adress, https://moodle.fstc.uni.lu, amazon.com, amazon.de.
Additionnally connection to an imap web server did not work with or without SSL encrypton.
Additionnally I could not connect to any instant messaging server. I tried MSN and ICQ.
You are VERY welcome.
Cheers kiepmad
Offline
thank you very much. i will try this out as soon as i get home. i'll file a bug at the main kernel bugtracker, that's why i wanted more information.
cheers Barde
Offline
thank you very much. i will try this out as soon as i get home. i'll file a bug at the main kernel bugtracker, that's why i wanted more information.
cheers Barde
Thanks for doing that.
I used to be surprised that I was still surprised by my own stupidity, finding it strangely refreshing.
Well, now I don't find it refreshing.
I'm over it!
Offline
Bug already filed at kernel.org...
But they seem to be focusing on the tcp_sack fix..which doesn't work for some of us.
Offline
I just did an Yaourt -Syu which included a minor kernel update, though I still had the same internet connection problems that we have been experiencing.
Anyway I read the bug report that Misfit138 posted a link to above & after using su I entered the following at the root prompt:
echo 0 > /proc/sys/net/ipv4/tcp_timestamps
I am able to use the current kernel, & my internet problems are no more!
I have no idea what that command does, but it came up as a worker in the bug report below:
http://bugzilla.kernel.org/show_bug.cgi?id=11721
Last edited by handy (2008-10-21 02:21:31)
I used to be surprised that I was still surprised by my own stupidity, finding it strangely refreshing.
Well, now I don't find it refreshing.
I'm over it!
Offline
Great work handy.
Add this to your /etc/sysctl.conf:
#Temporary workaround for tcp issue with 2.6.27
net.ipv4.tcp_timestamps = 0
Offline
Great work handy.
Add this to your /etc/sysctl.conf:
#Temporary workaround for tcp issue with 2.6.27 net.ipv4.tcp_timestamps = 0
I wondered whether the above command would be permanent.
Thanks for that info' I'll add it to the new thread:
I used to be surprised that I was still surprised by my own stupidity, finding it strangely refreshing.
Well, now I don't find it refreshing.
I'm over it!
Offline
thanks everyone. it seems as if the patch is already working and most probably will be in some future version of the kernel so we won't need the fix for ever hooray
cheers Barde
Offline
What patch?
I used to be surprised that I was still surprised by my own stupidity, finding it strangely refreshing.
Well, now I don't find it refreshing.
I'm over it!
Offline
Another thing to check is tcp_window_scaling. I have a similar issue even with older kernels on funny networks.
http://lwn.net/Articles/92727/
One time fix as root run:
sysctl -w net.ipv4.tcp_window_scaling=0
To make it persistent across reboots:
As root edit /etc/sysctl.conf
Add a line as follows:
net.ipv4.tcp_window_scaling=0
Offline
What patch?
http://bugzilla.kernel.org/show_bug.cgi?id=11721#c58 (listed some hours after your post ;-) )
This will be included in 2.6.27.x (with x beeing quite close to 2 i hope)
So either apply the patch or just wait for the next release. I have no time for a long compile so I just wait. Didn't test it myself, but it seems to relate very closely to my problem, referring from the comments and the problem (ordering of tcp options in the packet)
Offline
handy wrote:What patch?
http://bugzilla.kernel.org/show_bug.cgi?id=11721#c58 (listed some hours after your post ;-) )
This will be included in 2.6.27.x (with x beeing quite close to 2 i hope)
So either apply the patch or just wait for the next release. I have no time for a long compile so I just wait. Didn't test it myself, but it seems to relate very closely to my problem, referring from the comments and the problem (ordering of tcp options in the packet)
Thanks for the info'.
As it stands my system is working as well as it ever was, on the current kernel after taking the following actions:
Add this to your /etc/sysctl.conf:
#Temporary workaround for tcp issue with 2.6.27
net.ipv4.tcp_timestamps = 0
So what ill effect does turning off timestamps have on tcp?
Last edited by handy (2008-10-22 21:21:33)
I used to be surprised that I was still surprised by my own stupidity, finding it strangely refreshing.
Well, now I don't find it refreshing.
I'm over it!
Offline
It should not have any impact on your normal use. It can be used to measure round-trip times, I think.
However, it is still a work-around and on the patched kernel it is not necessary to turn it of. I doubt that you will ever see any differences when you just use this option and forget about it.
I think when you have to disable TCP_SACK with your hardware, this can possibly have a small performance impact. Nothing you would care of as a normal user I guess.
I would personally recommend setting on of these options if it helps, rather than patching the kernel, but I just not installing the new kernel for now and waiting for the fixed one is also an option. This is the way I am going, because I don't need the new kernel today. It's just that I will run into problems on arch when I update everything except the kernel, so I need to have a working 2.6.27 kernel somewhen.
Last edited by JonnyJD (2008-10-22 22:53:20)
Offline
I still need to disable tcp_sack in 2.6.27.4, but the mentioned patch is in the mainline kernel now. Either it is not in .4 yet, or it doesn't work for me.
EDIT:
I can't find the patch in http://www.kernel.org/pub/linux/kernel/ … g-2.6.27.4 so I assume it will be in the next release.
Last edited by JonnyJD (2008-10-28 00:42:58)
Offline
Did the following work on your system?
Add this to your /etc/sysctl.conf:
#Temporary workaround for tcp issue with 2.6.27
net.ipv4.tcp_timestamps = 0
I used to be surprised that I was still surprised by my own stupidity, finding it strangely refreshing.
Well, now I don't find it refreshing.
I'm over it!
Offline