Actions
Bug #1431
closedstream: last_ack update issue leading to stream gaps (2.0.x)
Affected Versions:
Effort:
Difficulty:
Label:
Updated by john kely about 9 years ago
I also find this issue when logging all sequence of arrival packets.
I think in segment loop, when sequence of segment is larger next expecting sequence, should not create a gap, need to wait for expecting packet arrive. In many cases, the expecting packet can arrive after a little or packet is retried in miss-packet case. Not need timeout for this because that with last_ack is updated correctly, if last_ack is larger sequence of first segment in segment_list, it certainly has a gap and will release stream.
Updated by Victor Julien about 9 years ago
If last_ack is updated properly, we know that the end host has received and acked the packet we are missing.
Updated by Victor Julien almost 9 years ago
- Target version changed from 2.0.8 to 2.0.9
Need to reconsider, the traffic may not be valid after all.
Updated by Victor Julien over 8 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Actions