From: Manfred Spraul <manfred@colorfullife.com>
To: dwd@bell-labs.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.16 through 2.2.18preX TCP hang bug triggered by rsync
Date: Tue, 23 Jan 2001 23:59:54 +0100 [thread overview]
Message-ID: <3A6E0CEA.ABD620F8@colorfullife.com> (raw)
In-Reply-To: <3A6E02E6.B3261E1@colorfullife.com>
I checked RFC793, and AFAICS Solaris is the culprit:
it sends out invalid packets, Linux ignores them and thus Linux doesn't
receive acks.
Which Solaris version do you use?
* The last valid ack from the Solaris computer is for byte 1583721, win
8760 (line 2078)
* No packet after line 2078 from the Solaris computer passed the
acceptability test from RFC793, page 69. Thus Linux ignores these
packets completely.
* Linux sends out packets up to 1591021:1592481(1460) without receiving
_valid_ acks, then it begins to retry 1583721:1585181(1460) every 2
seconds until the end of the tcpdump.
--
Manfred
-
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:[~2001-01-24 8:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 22:17 Linux 2.2.16 through 2.2.18preX TCP hang bug triggered by rsync Manfred Spraul
2001-01-23 22:59 ` Manfred Spraul [this message]
2001-01-24 20:03 ` kuznet
2001-01-24 20:34 ` Manfred Spraul
2001-01-24 20:42 ` kuznet
2001-01-25 18:35 ` kuznet
2001-01-24 20:56 ` Andi Kleen
2001-01-25 10:58 ` Matthias Andree
2001-01-25 12:17 ` James Sutherland
2001-01-25 12:27 ` Matthias Andree
2001-01-25 11:32 ` David S. Miller
2001-01-25 11:40 ` Andi Kleen
2001-01-25 11:44 ` David S. Miller
2001-01-25 11:56 ` Andi Kleen
2001-01-25 12:25 ` James Sutherland
-- strict thread matches above, loose matches on Subject: below --
2001-01-26 20:56 Dave Dykstra
2001-01-27 18:27 ` kuznet
2001-01-25 12:24 Studierende der Universitaet des Saarlandes
2001-01-25 12:34 ` Andi Kleen
2001-01-23 20:42 Dave Dykstra
2001-01-23 22:51 ` Dave Dykstra
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=3A6E0CEA.ABD620F8@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=dwd@bell-labs.com \
--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