From: Daniel Drake <dsd@gentoo.org>
To: John Heffner <jheffner@psc.edu>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.17 regression: Very slow net transfer from some hosts
Date: Tue, 11 Apr 2006 23:20:42 +0100 [thread overview]
Message-ID: <443C2BBA.5010804@gentoo.org> (raw)
In-Reply-To: <443C178B.3030805@psc.edu>
John Heffner wrote:
> This is almost certainly due to a buggy firewall that doesn't understand
> TCP window scaling. I've usually seen this in the past with OpenBSD
> firewalls. Do you have one of these in your path?
At home I'm behind a Linux gateway box currently running 2.6.15-rc6 - I
am connected through ethernet to that.
At my student house I am connected wirelessly to a Linksys WRT54Gv5
router (the model that doesnt run Linux).
I have reproduced it at both those locations (same ISP).
This is very familiar, and I just found the article I was thinking of:
http://lwn.net/Articles/92727/
I was also hit by that bug, on the same collection of websites, but that
particular problem was fixed for 2.6.8 or so. So I guess it is extremely
likely that my ISP has broken routers. nmap isn't able to identify the
OS of any ISP routers in my path.
It's a huge ISP over here, so contacting them over technical matters is
not easy...
Thanks,
Daniel
next prev parent reply other threads:[~2006-04-11 22:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 19:30 2.6.17 regression: Very slow net transfer from some hosts Daniel Drake
2006-04-11 19:21 ` Stephen Hemminger
2006-04-11 19:23 ` John Heffner
2006-04-11 20:03 ` Daniel Drake
2006-04-11 19:55 ` John Heffner
2006-04-11 20:53 ` Daniel Drake
2006-04-11 20:54 ` John Heffner
2006-04-11 22:20 ` Daniel Drake [this message]
2006-04-11 22:33 ` Stephen Hemminger
2006-04-12 0:06 ` Daniel Drake
2006-04-11 23:59 ` Stephen Hemminger
2006-04-12 0:32 ` John Heffner
2006-04-12 0:42 ` John Heffner
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=443C2BBA.5010804@gentoo.org \
--to=dsd@gentoo.org \
--cc=jheffner@psc.edu \
--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).