From: Mika Liljeberg <Mika.Liljeberg@welho.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.16: TCP shutdown generating infinite ACK storm
Date: Sun, 02 Dec 2001 13:48:57 +0200 [thread overview]
Message-ID: <3C0A1529.5D22EDDF@welho.com> (raw)
In-Reply-To: <1007290602.1892.2.camel@ixodes.goop.org>
Jeremy Fitzhardinge wrote:
> I'm looking at my box and a server at Tom's Hardware pounding each other
> with packets. It looks like Linux has got confused about sequence
> numbers (or maybe the other end is confused?).
Yes, it does look like a sequence synchronization problem.
> Naturally, this looks bad. After a while it seemed to stop of its own
> accord, I presume when something timed out of LAST_ACK. While it was
> happening, there were two sockets ixising to ad.tomshardware.com:
>
> tcp 1 1 ixodes.goop.org:33674 ad.tomshardware.co:http LAST_ACK
> tcp 1 1 ixodes.goop.org:33708 ad.tomshardware.co:http LAST_ACK
>
> I'm using 2.4.16 with no particularly special patches. The gateway
> machine is another 2.4.16 box doing NAT with ipchains emulation.
>
> Any other info needed?
If you can repeat this, you please run tcpdump with the -vv option in
order to get it to display the sequence numbers on ack packets as well.
It would also be good to see the last few packets of the connection (at
least the FIN packets).
BR,
MikaL
next prev parent reply other threads:[~2001-12-02 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 10:56 2.4.16: TCP shutdown generating infinite ACK storm Jeremy Fitzhardinge
2001-12-02 11:48 ` Mika Liljeberg [this message]
2001-12-02 16:23 ` Alan Cox
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=3C0A1529.5D22EDDF@welho.com \
--to=mika.liljeberg@welho.com \
--cc=jeremy@goop.org \
--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