Project

General

Profile

Actions

Bug #4229

closed

tcp/async: incorrect flagging of ACK values as invalid

Added by Victor Julien almost 2 years ago. Updated almost 2 years 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 1 (0 open1 closed)

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

Updated by Victor Julien almost 2 years ago

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

Updated by Victor Julien almost 2 years ago

  • Status changed from Assigned to In Progress
Actions #3

Updated by Victor Julien almost 2 years ago

  • Status changed from In Progress to Closed
Actions

Also available in: Atom PDF