Project

General

Profile

Actions

Bug #1431

closed
VJ VJ

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

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

Added by Victor Julien about 11 years ago. Updated over 10 years ago.

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

Description

JK Updated by john kely about 11 years ago Actions #1

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.

VJ Updated by Victor Julien about 11 years ago Actions #2

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

VJ Updated by Victor Julien almost 11 years ago Actions #3

  • Target version changed from 2.0.8 to 2.0.9

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

VJ Updated by Victor Julien over 10 years ago Actions #4

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

Also available in: PDF Atom