Benjamin LaHaise wrote:
On Tue, May 01, 2007 at 09:41:28PM +0400, Evgeniy Polyakov wrote:
Hmm, 2.2 machine in your test seems to behave incorrectly:
I am aware of that. However, I think that the loss of certain packets and
reordering can result in the same behaviour. What's more, is that this
behaviour can occur in real deployed systems. "Be strict in what you send
and liberal in what you accept." Both systems should be fixed, which is
what I'm trying to do.
Actually, you cannot get in this situation by loss or reordering of
packets, only be corruption of state on one side. It sends the FIN,
which effectively increases the sequence number by one. However, all
later segments it sends have an old lower sequence number, which are now
out of window.
Being liberal in what you accept is good to a point, but sometimes you
have to draw the line.
-John
-
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
