Open Information Security Foundation

10/19/2017

04:37 PM Suricata Bug #2230: valgrind memcheck - 4.0.0-dev (rev 1180687)

Seems we have those cases (with slight variations) with AFP and pcap - so would investigate a bit further for complet...

10/13/2017

02:40 AM Suricata Feature #2227: more detailed output about number of threads created

Yes indeed - I forgot that 1 receive thread!
Wonder if it is worthed adding that to the output with autofp? (aka som...

10/12/2017

03:09 PM Suricata Bug #2230 (New): valgrind memcheck - 4.0.0-dev (rev 1180687)

...

02:42 PM Suricata Bug #2229 (Assigned): mem leak AFP with 4.0.0-dev (rev 1180687)

...

02:30 PM Suricata Bug #2226: improve error message if stream memcaps too low

The issue goes away with Napatech (as confirmed by Philip) when increasing the stream and reassembly memcaps.

02:14 AM Suricata Bug #2226: improve error message if stream memcaps too low

I am reconfirming the config used in the napatech run - as i suspect the issue goes away after the memcaps are increa...

10/11/2017

02:25 PM Suricata Bug #2226: improve error message if stream memcaps too low

In the case of af-packet (v3):
When the memcaps are adjusted - stream.memcap=1GB and stream.reassembly.memcap=2GB
...

01:53 PM Suricata Bug #2228 (Closed): enforcing specific number of threads with autofp does not seem to work

Maybe related to https://redmine.openinfosecfoundation.org/issues/2227
The test machine is with 8 CPUs....

01:46 PM Suricata Feature #2227 (New): more detailed output about number of threads created

On a 8 core machine - ...

01:35 PM Suricata Bug #2226 (Closed): improve error message if stream memcaps too low

It seems af-packet and Napatech (reported and investigated by Philip Young) runmodes can not go beyond 117 threads.
...