Project

General

Profile

Actions
Copy link

Bug #4722

closed

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

Added by Victor Julien about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Victor Julien
Target version:
7.0.0-beta1
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 open — 1 closed)

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

Updated by Victor Julien about 3 years ago

  • Label Needs backport to 6.0 added
Actions
Copy link
 #2

Updated by Victor Julien about 3 years ago

  • Status changed from Assigned to Closed
Actions
Copy link
 #3

Updated by Victor Julien about 3 years ago

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

Also available in: Atom PDF