From: "David S. Miller" <davem@redhat.com>
To: jordy@napster.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, 6 Nov 2000 22:56:07 -0800 [thread overview]
Message-ID: <200011070656.WAA02435@pizda.ninka.net> (raw)
In-Reply-To: <3A07A4B0.A7E9D62@napster.com> (message from Jordan Mendelson on Mon, 06 Nov 2000 22:44:00 -0800)
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>
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.
Ok, something is "odd" at the win98 side, I quote the win98 log:
22:34:36.069773 64.124.41.179.8888 > 209.179.194.175.1084: P 1:19(18) ack 44 win 5840 (DF)
22:34:36.069837 64.124.41.179.8888 > 209.179.194.175.1084: P 19:553(534) ack 44 win 5840 (DF)
Linux sends 1-->553
Since this is in the win98 log, it saw this data, but refuses to
acknowledge it and the retransmit timeout expires on the Linux side.
22:34:39.049788 64.124.41.179.8888 > 209.179.194.175.1084: P 1:21(20) ack 44 win 5840 (DF)
So Linux resends 1-->21
22:34:39.051638 209.179.194.175.1084 > 64.124.41.179.8888: P 44:56(12) ack 21 win 65260 (DF)
Win98 sends data, and only acknowledges the resent data from Linux.
22:34:39.245138 64.124.41.179.8888 > 209.179.194.175.1084: P 21:555(534) ack 44 win 5840 (DF)
22:34:39.245208 64.124.41.179.8888 > 209.179.194.175.1084: P 557:1091(534) ack 56 win 5840 (DF)
Win98 machine receives bytes 21-->1091 from Linux, Linux also is
acknowledging Win98's data up to 56, but...
22:34:41.739438 209.179.194.175.1084 > 64.124.41.179.8888: P 44:456(412) ack 21 win 65260 (DF)
Win98 still claims it only saw up to byte 21 from Linux. Win98 also
resends its data, therefore it has not seen Linux's ACKs either.
And this goes on and on.
Just to be absolutely sure, 64.124.41.179 is the Linux machine, right?
If so, Win98 is dropping packets it did in fact receive correctly,
before Win98's TCP has a look at them.
WHOA, wait a second! From the Linux side log:
23:36:16.261533 64.124.41.179.8888 > 209.179.194.175.1084: P 1:21(20) ack 44 win 5840 (DF)
23:36:16.261669 64.124.41.179.8888 > 209.179.194.175.1084: P 21:557(536) ack 44 win 5840 (DF)
23:36:19.261055 64.124.41.179.8888 > 209.179.194.175.1084: P 1:21(20) ack 44 win 5840 (DF)
The equivalent packets from the win98 log:
22:34:36.069773 64.124.41.179.8888 > 209.179.194.175.1084: P 1:19(18) ack 44 win 5840 (DF)
22:34:36.069837 64.124.41.179.8888 > 209.179.194.175.1084: P 19:553(534) ack 44 win 5840 (DF)
22:34:39.049788 64.124.41.179.8888 > 209.179.194.175.1084: P 1:21(20) ack 44 win 5840 (DF)
(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?
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?
Later,
David S. Miller
davem@redhat.com
-
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:11 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 [this message]
2000-11-07 7:16 ` Jordan Mendelson
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=200011070656.WAA02435@pizda.ninka.net \
--to=davem@redhat.com \
--cc=jordy@napster.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