Hello!
> No, because no other packet is acking XSEQ+1! If you drop that packet and
> blindly ACK it, then host2 will enter TIME_WAIT, but you will stay in
> CLOSING! In my old dumps, host2 then ignored the retransmitted FIN,
> resulting in a stuck socket.
TIME-WAIT state exists exactly to catch other side sitting in LAST-ACK
and CLOSING. 8)
Now, return to my earlier mails and reread lines, where I said about
time-wait bug in 2.1 and early 2.2. They had broken time-wait, which
blackholed all retransmits, instead of ACKing.
So, theorem is proven finally, host2 was also linux and this bug has
been fixed. 8)
That's all?
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
