From: Mark Lord <lkml@rtr.ca>
To: Mark Lord <lkml@rtr.ca>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: 2.6.17: networking bug??
Date: Tue, 13 Jun 2006 11:00:12 -0400 [thread overview]
Message-ID: <448ED2FC.2040704@rtr.ca> (raw)
In-Reply-To: <448ECB09.3010308@rtr.ca>
Mark Lord wrote:
..
> The differences I see are widely varying "window sizes".
> What would cause this?
This is from (working) 2.6.16.18:
> IP silvy.localnet.56224 > 216-145-246-23.rev.dls.net.www: . ack 1 win 1460 <nop,nop,timestamp 730448 134760199>
> IP silvy.localnet.56224 > 216-145-246-23.rev.dls.net.www: P 1:607(606) ack 1 win 1460 <nop,nop,timestamp 730448 134760199>
> IP 216-145-246-23.rev.dls.net.www > silvy.localnet.56224: P 1:206(205) ack 607 win 32798 <nop,nop,timestamp 134760217 730448>
> IP silvy.localnet.56224 > 216-145-246-23.rev.dls.net.www: . ack 206 win 1728 <nop,nop,timestamp 730626 134760217>
This is from (failing) 2.6.17-rc6-git2:
> IP silvy.localnet.33472 > 216-145-246-23.rev.dls.net.www: . ack 1 win 92 <nop,nop,timestamp 4294759337 134771817>
> IP silvy.localnet.33472 > 216-145-246-23.rev.dls.net.www: P 1:607(606) ack 1 win 92 <nop,nop,timestamp 4294759337 134771817>
> IP silvy.localnet.33472 > 216-145-246-23.rev.dls.net.www: P 1:607(606) ack 1 win 92 <nop,nop,timestamp 4294760162 134771817>
> IP 216-145-246-23.rev.dls.net.www > silvy.localnet.33472: . ack 607 win 32798 <nop,nop,timestamp 134771918 4294760162>
Both kernels default to /proc/sys/net/ipv4/tcp_window_scaling == 1,
and 2.6.16.18 works regardless of whether I turn it off/on again.
But 2.6.17-rc6-git2 fails to work with the webserver at www.everymac.com
when /proc/sys/net/ipv4/tcp_window_scaling == 1. Setting this to 0
"fixes" the problem.
BUG.
next parent reply other threads:[~2006-06-13 15:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <448EC6F3.3060002@rtr.ca>
[not found] ` <448ECB09.3010308@rtr.ca>
2006-06-13 15:00 ` Mark Lord [this message]
2006-06-13 15:28 ` 2.6.17: networking bug?? Mark Lord
2006-06-13 16:58 ` Mark Lord
2006-06-13 17:22 ` Mark Lord
2006-06-13 17:39 ` John Heffner
2006-06-13 17:50 ` Linus Torvalds
2006-06-13 18:26 ` Mark Lord
2006-06-13 19:08 ` Mark Lord
2006-06-13 21:26 ` David Miller
2006-06-13 21:49 ` Mark Lord
2006-06-13 22:12 ` Rick Jones
2006-06-13 22:23 ` David Miller
2006-06-13 22:40 ` Rick Jones
2006-06-13 23:01 ` David Miller
2006-06-14 1:25 ` John Heffner
2006-06-13 23:22 ` Matt Mackall
2006-06-19 7:07 ` Helge Hafting
2006-06-14 5:18 ` Andi Kleen
2006-06-14 8:09 ` Daniel Drake
2006-06-13 18:28 ` John Heffner
2006-06-13 20:45 ` Barry K. Nathan
2006-06-13 22:09 ` Chase Venters
2006-06-13 22:23 ` David Miller
2006-07-02 17:39 ` Jan Knutar
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=448ED2FC.2040704@rtr.ca \
--to=lkml@rtr.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@osdl.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).