Project

General

Profile

Actions

Bug #4722

closed

flows: TCP flow timeout handling stuck if there is no traffic

Added by Victor Julien over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:
Needs backport to 6.0

Description

If traffic stops completely (e.g. a T-Rex test has finished) the flows the flow manager injects to the packet threads are never processed.


Related issues 1 (0 open1 closed)

Copied to Suricata - Bug #4733: flows: TCP flow timeout handling stuck if there is no trafficClosedVictor JulienActions
Actions #1

Updated by Victor Julien over 2 years ago

  • Label Needs backport to 6.0 added
Actions #2

Updated by Victor Julien over 2 years ago

  • Status changed from Assigned to Closed
Actions #3

Updated by Victor Julien over 2 years ago

  • Copied to Bug #4733: flows: TCP flow timeout handling stuck if there is no traffic added
Actions

Also available in: Atom PDF