-
Notifications
You must be signed in to change notification settings - Fork 532
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIX: Adjust so-import-pcap so that suricata works when it is pcapengine #12969
Milestone
Comments
dougburks
added a commit
that referenced
this issue
May 8, 2024
dougburks
added a commit
that referenced
this issue
May 8, 2024
…ch-1 FIX: Adjust so-import-pcap so that suricata works when it is pcapengine #12969
Tested and verified that so-import-pcap ran successfully and Suricata alerts appeared in Dashboards with pcapengine set to suricata:
Tested and verified with pcapengine set to steno:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When pcapengine is SURICATA or TRANSITION, suricata is configured to write full packet capture. When running so-import-pcap, suricata then fails because suricata.yaml specifies a pcap directory that is not specified in the docker volume mappings in so-import-pcap. For so-import-pcap, we don't really need suricata to write full packet capture so we can specify the mapping as /dev/null.
The text was updated successfully, but these errors were encountered: