DebianThis forum is for the discussion of Debian Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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 18.104.22.168-slh-up-1 and not a "vanilla" Debian kernel.
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:
might have missed something but... connecting to Debian.org problems
Iceweasel will not connect with 'www.debian.org', previous posts suggested my set up was wrong but this seems odd, have debian servers got extra security I do not know about or is my router an issue, this has no security on it as I was hoping to use it as a switch; any thoughts?
Distribution: Debian Wheezy, Jessie, Sid/Experimental, playing with LFS.
Fred this thread is about 5 weeks off being 6 years old. May I recommend you start a new thread because 99.9999999% chance your issue is different to the OPs issue. You really must have searched through the dungeons to rake this old beasty up.