DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
There are less than 24 hours left to vote in the 2011 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Wtf? Using echo 0 >/proc/sys/net/ipv4/tcp_window_scaling and I can connect to the site.
With it on I can't even with firewall off and a direct connection to my cable modem. Weird.
Is that something that is in the kernel?
If it is , it might explain why I couldn't connect and others using "pure" Debian Sid could; since I am using a Sidux kernel 2.6.18.5-slh-up-1 and not a "vanilla" Debian kernel.
The funny thing is, on Ubuntu this value is set to 1, not 0. Exactly as on my Slackware box. So it's probably not this value directly, but something linked to it.
It appears to be an issue with TCP window scaling and broken routers. The scaling options have changed as of kernel 2.6.17 and the problem seems to occur if you have a lot of RAM and of course a broken network equipment between you and the server.
Setting back the values to those of an earlier kernel does the trick:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.