Project

General

Profile

Actions

Bug #1431

closed

stream: last_ack update issue leading to stream gaps (2.0.x)

Added by Victor Julien almost 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

Actions #1

Updated by john kely almost 8 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.

Actions #2

Updated by Victor Julien almost 8 years ago

If last_ack is updated properly, we know that the end host has received and acked the packet we are missing.

Actions #3

Updated by Victor Julien over 7 years ago

  • Target version changed from 2.0.8 to 2.0.9

Need to reconsider, the traffic may not be valid after all.

Actions #4

Updated by Victor Julien over 7 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF