[Oisf-users] Discrepancies in Snort and Suricata alerts

fatema bannatwala fatema.bannatwala at gmail.com
Mon Oct 8 14:56:00 UTC 2018

> Would you be able to test this pull request?

> https://github.com/OISF/suricata/pull/3497

> It adds a counter 'tcp.wrong_thread' that is incremented if TCP packets
> come in on the wrong thread.

I pulled the zip from:

And when ran autogen.sh , got the following error:

[~suricata-53f345e90ed284691d34e6f843e874812b079d80]$ ./autogen.sh
which: no libtoolize in (/sbin:/bin:/usr/sbin:/usr/bin)
which: no glibtoolize in (/sbin:/bin:/usr/sbin:/usr/bin)
Failed to find libtoolize or glibtoolize, please ensure it is installed and
accessible via your PATH env variable

I currently run suricata 4.0.4 on that box, is this a new pre-requisite
requirement need to be installed?

Also, I am now wondering, as a normal user perspective, is it just me who
is having trouble with multi-threading with Suricata,  no one else
experienced the similar situation or maybe never realized that some tcp
based alerts are missing?
I followed the installation and guide from SepTune doc so not sure what I

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openinfosecfoundation.org/pipermail/oisf-users/attachments/20181008/e6a69263/attachment.html>

More information about the Oisf-users mailing list