netdev
[Top] [All Lists]

Re: ipv6 stack seems to forget to send ACKs

To: Fabio Massimo Di Nitto <fabbione@xxxxxxxxxxxx>, Wichert Akkerman <wichert@xxxxxxxxx>
Subject: Re: ipv6 stack seems to forget to send ACKs
From: Andrew McGregor <andrew@xxxxxxxxxxxxxx>
Date: Thu, 09 Jan 2003 08:59:53 +1300
Cc: netdev@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.51.0301081849550.564@diapolon.int.fabbione.net>
References: <20030108130850.GQ22951@wiggy.net> <Pine.LNX.4.51.0301081849550.564@diapolon.int.fabbione.net>
Sender: netdev-bounce@xxxxxxxxxxx


--On Wednesday, January 08, 2003 19:05:36 +0100 Fabio Massimo Di Nitto <fabbione@xxxxxxxxxxxx> wrote:


I was able to reproduce the problem again. I have been using ethereal to sniff instead of tcpdump and gave out some more info.

basically the icecast server at certain time (but i can't predict
exactly in which situations) just send a FIN, ACK packet to the client.
Basically to close the connection and after a few packets the client of
course answer.What is strange that in the meanwhile there are still 3/4
data packets coming from the server to the client.

Regarding the network side I noticed the following:

an average of 500ms to ping6 the server and 0 pkt loss
few seconds before the FIN, ACK (server->client) and for about 6 pkts the
average jumped to 2000ms

I suspect that this network flap made the server thinking about
<insert_here_whatever_term_is_more_appropriate> and decided to close
the connection.

Probably on the server's side it got an ICMP Host Unreachable or two as some router updated its tables, and decided to close the connection. The FIN jumped the queue in one/several of the routers in the path, so it got reordered relative to the data. This would imply that the router in question had its route to you back by the time the FIN got there.


Wierd, but far from impossible.


The full ethereal dump is available at http://www.fabbione.net/ice-xmms-ipv6.dump.bz2

but PLEASE note that it is a 10MB file and Im on a slow adsl line so be
"nice".

I think you provided enough info to tell what happened.


Fabio

PS Im afraid/happy that anyway the problem is not related to the kernel
version we are running.

Doesn't look like a kernel problem.

Someone's got a dodgy link or a routing problem.

Andrew



<Prev in Thread] Current Thread [Next in Thread>