Project

General

Profile

Actions

Bug #3459

closed

SURICATA STREAM pkt seen on wrong thread

Added by Samiux A about 4 years ago. Updated about 2 years ago.

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

Description

Suricata version : 4.1.6
Hyperscan : enabled
Running mode : af-packet IPS
runmode : workers

When running suricata is in the above settings, the fast.log got a lot of this kind of messages :

[**] [1:2210059:1] SURICATA STREAM pkt seen on wrong thread [**] [Classification: (null)] [Priority: 3] {TCP}

However, when autofp is set, the message gone.

Any idea?

Actions #1

Updated by Victor Julien about 4 years ago

Are you able to try 5.0.1? In 5.0.1 the thread id tracking is done per direction.

Actions #2

Updated by Andreas Herz about 2 years ago

  • Status changed from New to Closed

Hi, we're closing this issue since there have been no further responses.
If you think this issue is still relevant, try to test it again with the
most recent version of suricata and reopen the issue. If you want to
improve the bug report please take a look at
https://redmine.openinfosecfoundation.org/projects/suricata/wiki/Reporting_Bugs

Actions

Also available in: Atom PDF