Hello!
> No, i think you misinterpreted the problem. The two ends entered the
> synchronized CLOSING (or CLOSE_WAIT?) state. Linux would drop a critical
> packet, and thus would not exit the synchronized state when the other end
> did. This is a Bad Thing. It has nothing to do with TIME_WAIT at all.
I repeat, _this_ _is_ _impossible_.
Look at your sample in code, it is invalid. It cannot be
generated by some real TCP stack.
OK, if you cannot regenerate the sequence of events
(I know, it is not so easy), I still can assume that you did
a misprint there. Edit that sample, at least.
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
