Bug 1103192
| Summary: | suricata 2.0 not seeing any traffic | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Lance Lassetter <lancelassetter> | ||||
| Component: | suricata | Assignee: | Steve Grubb <sgrubb> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | athmanem, lancelassetter, sgrubb | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-06-29 20:52:33 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
The default suricata.yaml file is set for eth0. That may not exist because of the new device naming convention. For example, I have to edit it to be p4p1. There is also a newer suricata-2.0.1 in updates-testing that has updated configuration docs. It also includes a config file I found missing - maybe that is partly the problem? You might give that a try also. It won't necessarily fix your problem, but the newer docs and extra rules will help. Where do I set suricata to listen on p10p1 when running in nfqueue mode? This would be very helpful. I think it depends on having certain things in your iptables rules: https://redmine.openinfosecfoundation.org/projects/suricata/wiki/Setting_up_IPSinline_for_Linux I have the iptables rules as directed in suricata.yaml and the howto. Still suricata is seeing no traffic. Also the mailing list isn't being that responsive to the problem. Steve, thanks for your prompt reply. http.log is being populated. fast.log is not. drop.log is not.
This is with iptables rule "iptables -A FORWARD -m mark ! --mark 1/1 -j NFQUEUE --queue-num 2"
in suricata.yaml:
nfq:
mode: repeat
repeat-mark: 1
repeat-mask: 1
route-queue: 2
batchcount: 3
fail-open: yes
- drop:
enabled: yes
filename: drop.log
append: yes
filetype: regular #
And suricata run as: /sbin/suricata -c /etc/suricata/suricata.yaml -q 2 I compiled 1.4.7 from source downloaded from the Suricata site and now drop.log is working. So this must just affect Fedora and Suricata 2.0 or 2.0.1? Not using Fedora testing repo but did enable it to see if Suricata 2.0.1 was any different. This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 900818 [details] suricata.yaml for suricata 2.0 Description of problem: Since release suricata-2.0-1.fc20.x86_64 only logfiles being populated are eve.json and stats log. drop.log, http.log, fast.log, eve.json, and unified2.alert are all enabled. Suricata doesn't seem to be seeing any traffic. suricata is run "suricata -c /etc/suricata/suricata.yaml -q 0" with iptables rule "iptables -A FORWARD -m mark ! --mark 1/1 -j NFQUEUE --queue-num 0" The only other applicable setting in suricata yaml is: nfq: mode: repeat repeat-mark: 1 repeat-mask: 1 Version-Release number of selected component (if applicable): Fedora 20 using stable repos. How reproducible: Every time. Steps to Reproduce: 1. Delete suricata.yaml 2. "yum reinstall suricata" 3. Enable above steps and start suricata. "systemctl status suricata shows suricata as running as normal and rules loaded." Actual results: Logs not populated/suricata not seeing any traffic besides eve.jason log. Expected results: At least drop.log to be populated showing suricata is successfully run in IPS mode. Additional info: Here is my suricata.yaml