Firestarter init fails on system boot when NetworkManager is used
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firestarter (Debian) |
Fix Released
|
Unknown
|
|||
firestarter (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Firestarter init script (/etc/init.
The following error message is displayed:
Starting the Firestarter firewall: failed.
Manual startup fails with:
/etc/firestarte
External network device eth0 is not ready. Aborting..
A resolution might be to adding a firestarter script in /usr/share/
NOTE: This won't work with Edgy Eft in which the problem persists. If you wish to work around this problem in Edgy Eft, then make sure you place for example 50firestarter in /etc/NetworkMan
Related branches
Changed in firestarter: | |
status: | Unconfirmed → Confirmed |
Changed in firestarter: | |
assignee: | nobody → mrpouit |
status: | Confirmed → In Progress |
Changed in firestarter: | |
status: | Unknown → Unconfirmed |
Changed in firestarter: | |
assignee: | mrpouit → nobody |
status: | Fix Committed → Fix Released |
Changed in firestarter: | |
status: | New → Fix Released |
I am running Firestarter 1.0.3 and the latest NetworkManager from the code repository (the NetworkManager applet says 0.6.0). I am able to start both applications at startup without any errors. What versions are you running?
As a side note, I get a similar error to "External network device eth0 is not ready" from the Firestarter GUI, but only when eth0 was not able to start due to the cable not being plugged in at startup. This occurs regardless of NetworkManager being installed or not. This makes me think that for some reason your install of NetworkManager isn't bringing up your eth0 device before Firestarter tries to begin, so Firestarter fails. This wouldn't be a problem with Firestarter, but possibly with the start time of NetworkManager on your system.