From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: 2.6.17.1: fails to fully get webpage Date: Wed, 28 Jun 2006 20:47:09 -0700 (PDT) Message-ID: <20060628.204709.41634813.davem@davemloft.net> References: <20060629015915.GH2149@zip.com.au> <20060628.194627.74748190.davem@davemloft.net> <20060629030923.GI2149@zip.com.au> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org Return-path: Received: from dsl027-180-168.sfo1.dsl.speakeasy.net ([216.27.180.168]:65491 "EHLO sunset.davemloft.net") by vger.kernel.org with ESMTP id S1751156AbWF2DrK (ORCPT ); Wed, 28 Jun 2006 23:47:10 -0400 To: cat@zip.com.au In-Reply-To: <20060629030923.GI2149@zip.com.au> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org From: CaT Date: Thu, 29 Jun 2006 13:09:23 +1000 > Yup. Must've. Just tried it now and setting tcp_window_scaling to 0 > makes the site load. Sorry about that. Looks like I'll have to remember > to make sure that gets set to zero on any servers I wind up having to > upgrade to 2.6.17 and beyond. > > Bugger. :/ You can save yourself that hassle by informing the site admin of the affected site that they have a firewall that misinterprets the RFC standard window scaling field of the TCP headers. These devices assume it is zero because they don't remember the window scale negotiated at the beginning of the TCP connection. Your TCP performance will suffer greatly if you disable window scaling across the board. It means that only a 64K window will be usable by TCP, and you'll not be able to fill the pipe. Please don't use a screwdriver to pound in a nail :)