Project

General

Profile

Bug #4229

tcp/async: incorrect flagging of ACK values as invalid

Added by Victor Julien 8 months ago. Updated 7 months ago.

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

Description

In an async session where we only see the toclient side, the `next_win` is not properly initialized leading to invalid ack events for correct ACKs.


Related issues

Copied from Bug #4228: tcp/async: incorrect flagging of ACK values as invalidClosedVictor JulienActions
#1

Updated by Victor Julien 8 months ago

  • Copied from Bug #4228: tcp/async: incorrect flagging of ACK values as invalid added
#2

Updated by Victor Julien 7 months ago

  • Status changed from Assigned to In Progress
#3

Updated by Victor Julien 7 months ago

  • Status changed from In Progress to Closed

Also available in: Atom PDF