tcp: compare with correct m_recover for entering CA_RECOVERY or not (!156) · Merge requests · nsnam / ns-3-dev

Xiuchao Wu requested to merge xiuchao/ns-3-dev:tcp-enter-recovery into master Jan 02, 2020

When sequence number is advanced significantly between two consecutive packet loss events, one bug in NS-3 TCP model will be triggerred and TCP sender fails to enter into CA_RECOVERY state. This change fixed this issue by comparing m_highRxAckMark with m_recover effectively only when m_recover has been set correctly.

tcp: compare with correct m_recover for entering CA_RECOVERY or not

Merge request reports