On Tue, May 01, 2007 at 01:54:03PM -0400, John Heffner wrote:
> Looking at your trace, it seems like the behavior of the test system
> 192.168.2.2 is broken in two ways. First, like you said it has broken
> state in that it has forgotten that it sent the FIN. Once you do that,
> the connection state is corrupt and all bets are off. It's sending an
> out-of-window segment that's getting tossed by Linux, and Linux
> generates an ack in response. This is in direct RFC compliance. The
> second problem is that the other system is generating these broken acks
> in response to the legitimate acks Linux is sending, causing the ack
> war. I can't really guess why it's doing that...
I know it's a bug, and I'm trying to fix it, but that doesn't change the
fact that A) the system is already deployed and B) Linux is not retransmitting
the FIN, which (from Linux's point of view) remains unacknowledged by the
other side. The patch might be wrong, but the goal of fixing the behaviour
isn't.
-ben
--
"Time is of no importance, Mr. President, only life is important."
Don't Email: <[EMAIL PROTECTED]>.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
