From: bert hubert <ahu@ds9a.nl>
To: Bjorn Wesen <bjorn.wesen@axis.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What is TCPRenoRecoveryFail ?
Date: Thu, 28 Feb 2002 00:00:46 +0100 [thread overview]
Message-ID: <20020228000046.A26358@outpost.ds9a.nl> (raw)
In-Reply-To: <20020227152705.A18366@outpost.ds9a.nl> <Pine.LNX.3.96.1020227153315.18713F-101000@fafner.axis.se>
In-Reply-To: <Pine.LNX.3.96.1020227153315.18713F-101000@fafner.axis.se>; from bjorn.wesen@axis.com on Wed, Feb 27, 2002 at 06:33:43PM +0000
On Wed, Feb 27, 2002 at 06:33:43PM +0000, Bjorn Wesen wrote:
> > Please show a tcpdump -v of this happening, including the initial SYN
> > packets. I strongly suspect something in your network of mucking with TCP
> > options.
>
> Ok this is mangled by the email client but i attached the binary dump of
> the relevant packets. The dump is taken on the windows machine, which
> complicates the analysis because perhaps the network card itself is
> screwing up, but that is a low probability because all succeeding
This dump is somewhat inconclusive. I miss the SYN packets, but I'm
especially interested in this bit:
> 23:46:43.011000 10.13.18.46.http > dh10-13-18-213.axis.se.squid: . [tcp
> sum ok] 7300:8760(1460) ack 1 win 5840 (DF) (ttl 64, id 37963, len 1500)
> 23:46:43.011000 dh10-13-18-213.axis.se.squid > 10.13.18.46.http: . [tcp
> sum ok] ack 4380 win 8760 (DF) (ttl 128, id 55373, len 40)
> 23:46:43.011000 10.13.18.46.http > dh10-13-18-213.axis.se.squid: . [tcp
> sum ok] 8760:10220(1460) ack 1 win 5840 (DF) (ttl 64, id 37964, len 1500)
> 23:46:43.011000 dh10-13-18-213.axis.se.squid > 10.13.18.46.http: . [tcp
> sum ok] ack 4380 win 8760 (DF) (ttl 128, id 55629, len 40)
> 23:46:43.012000 10.13.18.46.http > dh10-13-18-213.axis.se.squid: P [tcp
> sum ok] 10220:11680(1460) ack 1 win 5840 (DF) (ttl 64, id 37965, len 1500)
> 23:46:43.012000 dh10-13-18-213.axis.se.squid > 10.13.18.46.http: . [tcp
> sum ok] ack 4380 win 8760 (DF) (ttl 128, id 55885, len 40)
>
> .. long timeout here until the server finally gives up the connection ..
how does this continue? I see the linux machine continuing to send data with
higher sequence numbers, but how does it end? It looks like the linux
machine never sent anything beyond 11680, relative.
To know more, dump at both ends. I really think something in between is
messing up - either a network adaptor or a ""smart"" network element.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2002-02-27 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 13:45 Bjorn Wesen
2002-02-27 14:27 ` bert hubert
2002-02-27 18:22 ` Bjorn Wesen
2002-02-27 23:00 ` bert hubert [this message]
2002-02-27 23:13 ` Bjorn Wesen
[not found] <Pine.LNX.3.96.1020227144128.18713E-100000@fafner.axis.se.suse.lists.linux.kernel>
2002-02-27 14:46 ` Andi Kleen
2002-02-27 17:03 Nivedita Singhvi
2002-02-27 17:06 ` David S. Miller
2002-02-27 17:25 Nivedita Singhvi
2002-02-28 0:14 Nivedita Singhvi
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=20020228000046.A26358@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=bjorn.wesen@axis.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
all inboxes | Powered by JetHome®