[lkml]   [2001]   [Dec]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.4.16: TCP shutdown generating infinite ACK storm
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
> tcp 1 1 LAST_ACK
> tcp 1 1 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).


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:18    [W:0.070 / U:2.420 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site