From: Mika Liljeberg <Mika.Liljeberg@welho.com>
To: kuznet@ms2.inr.ac.ru
Cc: davem@redhat.com, linux-kernel@vger.kernel.org, mika.liljeberg@nokia.com
Subject: Re: TCP LAST-ACK state broken in 2.4.17-pre2
Date: Thu, 13 Dec 2001 21:30:04 +0200 [thread overview]
Message-ID: <3C1901BC.C5E7936C@welho.com> (raw)
In-Reply-To: <200112131759.UAA01376@ms2.inr.ac.ru>
kuznet@ms2.inr.ac.ru wrote:
> This is not related to that problem.
I believe you. Nevertheless, it appears to be a problem that happens in
the LAST-ACK state.
> Please, make cat /proc/net/tcp at this point.
I'll do that if it happens again.
> To be honest I do not believe
> that tcpdump finishes _here_. When will retransmit timer expire? Taking
> into account that 10.0.5.3 has rto of 14 seconds (distance between retransmits
> of its FIN :-)), linux can have even more. In the case of such bad connection
> closing fin-wait-2 via abort is pretty normal.
I'm afraid it did end there. :( The data transfer was unidirectional
from the remote towards the Linux machine. During the SYN exchange the
RTT is less than one second. The rest is queuing delay. So Linux should
have a fairly low RTO. There were no FIN retransmissions, I'm sorry to
say.
> Alexey
Cheers,
MikaL
next prev parent reply other threads:[~2001-12-13 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 18:16 TCP LAST-ACK state broken in 2.4.17-pre2 Mika Liljeberg
2001-12-10 18:34 ` kuznet
2001-12-10 18:54 ` Mika Liljeberg
2001-12-11 17:51 ` kuznet
2001-12-12 20:31 ` Mika Liljeberg
2001-12-13 17:59 ` kuznet
2001-12-13 19:30 ` Mika Liljeberg [this message]
2001-12-13 19:38 ` kuznet
2001-12-11 0:13 ` David S. Miller
2001-12-11 17:24 ` kuznet
-- strict thread matches above, loose matches on Subject: below --
2001-12-13 10:19 Pasi Sarolahti
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=3C1901BC.C5E7936C@welho.com \
--to=mika.liljeberg@welho.com \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.liljeberg@nokia.com \
/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