From: David Miller <davem@davemloft.net>
To: cat@zip.com.au
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.17.1: fails to fully get webpage
Date: Wed, 28 Jun 2006 20:47:09 -0700 (PDT) [thread overview]
Message-ID: <20060628.204709.41634813.davem@davemloft.net> (raw)
In-Reply-To: <20060629030923.GI2149@zip.com.au>
From: CaT <cat@zip.com.au>
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 :)
next prev parent reply other threads:[~2006-06-29 3:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 1:59 2.6.17.1: fails to fully get webpage CaT
2006-06-29 2:46 ` David Miller
2006-06-29 3:09 ` CaT
2006-06-29 3:47 ` David Miller [this message]
2006-06-29 4:18 ` CaT
2006-06-29 14:50 ` Bill Davidsen
2006-06-29 22:50 ` CaT
2006-07-05 0:55 ` possible dos / wsize affected frozen connection length (was: Re: 2.6.17.1: fails to fully get webpage) CaT
2006-07-05 11:54 ` linux-os (Dick Johnson)
2006-07-10 23:23 ` CaT
2006-07-13 12:11 ` possible dos / wsize affected frozen connection length Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060628.204709.41634813.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cat@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).