[Ns-bugs] [Bug 1112] TCP goes to dead-lock when both segment-retransmit and ACK-loss occurs
code at nsnam.ece.gatech.edu
Thu Sep 1 13:55:08 PDT 2011
--- Comment #4 from Ryan Padilla <allidap623 at byu.net> 2011-09-01 16:55:06 EDT ---
I'm not sure to create a good test case for this because, without directly
changing the tcp code, I can't directly test the problem. I can only create a
situation where the problem is likely to appear, not guaranteed to appear.
The two these that need to occur for the two bugs to occur are:
* lost ACK, which the sender responds to by sending more data with the same
sequence number (and potentially a larger packet size because more data has
* two back to back timeouts, which cause the connection to hang because
sequence numbers aren't update correctly in the buffer during retransmissions
I am able to verify the bugs right now by running scenarios where contention is
high, having TcpSocketBase logging enabled and look through the logs to find
which connections died ( if any ) and why.
I can only create high contention among nodes, not guarantee or force ACK loss
to occur. At least, I don't know how to do it right now. Any suggestions would
Configure bugmail: https://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the Ns-bugs