From: Jordan Mendelson <jordy@napster.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, kuznet@ms2.inr.ac.ru
Subject: Re: Poor TCP Performance 2.4.0-10 <-> Win98 SE PPP
Date: Mon, 06 Nov 2000 23:16:21 -0800 [thread overview]
Message-ID: <3A07AC45.DCC961FF@napster.com> (raw)
In-Reply-To: <3A07662F.39D711AE@napster.com> <200011070428.UAA01710@pizda.ninka.net> <3A079127.47B2B14C@napster.com> <200011070533.VAA02179@pizda.ninka.net> <3A079D83.2B46A8FD@napster.com> <200011070603.WAA02292@pizda.ninka.net> <3A07A4B0.A7E9D62@napster.com> <200011070656.WAA02435@pizda.ninka.net>
"David S. Miller" wrote:
>
> Date: Mon, 06 Nov 2000 22:44:00 -0800
> From: Jordan Mendelson <jordy@napster.com>
>
> Attached to this message are dumps from the windows 98 machine using
> windump and the linux 2.4.0-test10. Sorry the time stamps don't match
> up.
>
> (ie. Linux sends bytes 1:21 both the first time, and when it
> retransmits that data. However win98 "sees" this as 1:19 the first
> time and 1:21 during the retransmit by Linux)
>
> That is bogus. Something is mangling the packets between the Linux
> machine and the win98 machine. You mentioned something about
> bandwidth limiting at your upstream provider, any chance you can have
> them turn this bandwidth limiting device off?
It actually turns out that that problem with bandwidth was fixed
yesterday, so this can not be the problem here and yes, 64.124.41.179 is
a linux box. :)
> Or maybe earthlink is using some packet mangling device?
>
> It is clear though, that something is messing with or corrupting the
> packets. One thing you might try is turning off TCP header
> compression for the PPP link, does this make a difference?
Actually, there has been several reports that turning header compression
does help.
Jordan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-07 7:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 2:17 Poor TCP Performance 2.4.0-10 <-> Win98 SE PPP Jordan Mendelson
2000-11-07 4:28 ` David S. Miller
2000-11-07 5:20 ` Jordan Mendelson
2000-11-07 5:33 ` David S. Miller
2000-11-07 6:13 ` Jordan Mendelson
2000-11-07 6:03 ` David S. Miller
2000-11-07 6:44 ` Jordan Mendelson
2000-11-07 6:56 ` David S. Miller
2000-11-07 7:16 ` Jordan Mendelson [this message]
2000-11-07 7:12 ` David S. Miller
2000-11-07 7:32 ` Jordan Mendelson
2000-11-07 7:27 ` David S. Miller
2000-11-07 9:41 ` Andi Kleen
2000-11-07 9:57 ` David S. Miller
2000-11-07 12:22 ` Alan Cox
2000-11-07 12:10 ` David S. Miller
2000-11-07 9:42 ` Andi Kleen
2000-11-07 18:13 ` Jordan Mendelson
2000-11-07 9:38 ` Rogier Wolff
2000-11-07 9:58 ` David S. Miller
2000-11-07 10:36 ` Rogier Wolff
2000-11-07 22:43 ` Lincoln Dale
2000-11-07 7:03 ` Andi Kleen
2000-11-07 6:59 ` David S. Miller
2000-11-07 7:16 ` Andi Kleen
2000-11-07 7:14 ` David S. Miller
2000-11-07 9:35 ` Rogier Wolff
2000-11-07 10:00 ` David S. Miller
[not found] <3A076701.F437F88B@napster.com>
2000-11-07 3:44 ` Jordan Mendelson
2000-11-07 4:29 ` David S. Miller
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=3A07AC45.DCC961FF@napster.com \
--to=jordy@napster.com \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@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