Bug 1227085 - Have Suricata start after the network is online.
Summary: Have Suricata start after the network is online.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: suricata
Version: 22
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Steve Grubb
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-01 22:31 UTC by Jason Ish
Modified: 2016-03-16 16:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-16 16:20:35 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jason Ish 2015-06-01 22:31:45 UTC 
Using the default configuration provided by Fedora, Suricata will fail to start if eth0 is DHCP assigned.  Having it start after network-online.target resolves this issue.

Steps to Reproduce:
1. yum install suricata
2. systemctl enable suricata
3. reboot

Suricata will not be started on boot.

By adding "network-online.tar.get" to the After line in suricata.service, Suricata will reliably start using the default configuration on a basically default install of Suricata.
Comment 1 Steve Grubb 2016-03-16 16:20:35 UTC 
Pushed the fix into git. It will be in the next build. Thanks for reporting the issue.
Note You need to log in before you can comment on or make changes to this bug.