Message-ID: <3C1901BC.C5E7936C@welho.com>
Date: Thu, 13 Dec 2001 21:30:04 +0200
From: Mika Liljeberg <Mika.Liljeberg@welho.com>
MIME-Version: 1.0
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
In-Reply-To: <200112131759.UAA01376@ms2.inr.ac.ru>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/