From: Gregory Maxwell <greg@linuxpower.cx>
To: Ookhoi <ookhoi@dds.nl>
Cc: Vibol Hou <vibol@khmer.cc>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
sim@stormix.com
Subject: Re: 2.4 tcp very slow under certain circumstances (Re: netdev issues (3c905B))
Date: Wed, 21 Feb 2001 08:12:02 -0500 [thread overview]
Message-ID: <20010221081202.C4447@xi.linuxpower.cx> (raw)
In-Reply-To: <HDEBKHLDKIDOBMHPKDDKMEGDEFAA.vibol@khmer.cc> <20010221104723.C1714@humilis>
In-Reply-To: <20010221104723.C1714@humilis>; from ookhoi@dds.nl on Wed, Feb 21, 2001 at 10:47:24AM +0100
On Wed, Feb 21, 2001 at 10:47:24AM +0100, Ookhoi wrote:
[snip]
> We have exactly the same problem but in our case it depends on the
> following three conditions: 1, kernel 2.4 (2.2 is fine), 2, windows ip
> header compression turned on, 3, a free internet access provider in
> Holland called 'Wish' (which seemes to stand for 'I Wish I had a faster
> connection').
> If we remove one of the three conditions, the connection is oke. It is
> only tcp which is affected.
> A packet on its way from linux server to windows client seems to get
> dropped once and retransmitted. This makes the connection _very_ slow.
[snip]
It's been true for some time now that there are several firewalls, RAS, and
NAT devices that break TCP connections in subtile but horrible ways when they
encounter SACK, timestamps, have header compression enabled, or other
'exotic' features.
Has anyone compiled a list of such bugs so that a test application could be
created?
prev parent reply other threads:[~2001-02-21 13:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 0:06 netdev issues (3c905B) Vibol Hou
2001-02-21 0:21 ` Martin Moerman
2001-02-21 0:34 ` Vibol Hou
2001-02-21 9:47 ` 2.4 tcp very slow under certain circumstances (Re: netdev issues (3c905B)) Ookhoi
2001-02-21 10:57 ` David S. Miller
2001-02-21 11:33 ` Ookhoi
2001-02-21 17:17 ` Ookhoi
2001-02-21 19:06 ` Vibol Hou
2001-02-21 19:22 ` Vibol Hou
2001-02-21 22:30 ` Jordan Mendelson
2001-02-22 8:28 ` Ookhoi
2001-02-21 23:49 ` Jordan Mendelson
2001-02-21 23:52 ` David S. Miller
2001-02-22 0:10 ` Jordan Mendelson
2001-02-22 0:50 ` Jordan Mendelson
2001-02-27 0:21 ` Simon Kirby
2001-02-27 0:26 ` David S. Miller
2001-02-21 13:12 ` Gregory Maxwell [this message]
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=20010221081202.C4447@xi.linuxpower.cx \
--to=greg@linuxpower.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=ookhoi@dds.nl \
--cc=sim@stormix.com \
--cc=vibol@khmer.cc \
/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