Bug 16421 - error message when opening Firestarter - conflict between Firestarter and NetworkManager?
Summary: error message when opening Firestarter - conflict between Firestarter and Net...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Colin Guthrie
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-19 21:13 CEST by macxi
Modified: 2015-11-11 18:38 CET (History)
0 users

See Also:
Source RPM: firestarter-1.0.3-23.mga5.x86_64.rpm
CVE:
Status comment:


Attachments

Description macxi 2015-07-19 21:13:43 CEST
Description of problem:
After installing the Firestarter in Mageia 5, KDE, 64, after I try to open the message appears:

"External network device eth0 is not ready. Aborting"

I found a possible solution for this error in:
https://help.ubuntu.com/community/Firestarter

It has been reported that there is a conflict between Firestarter and NetworkManager when booting that can cause the firewall policies to not initialize correctly. A possible workaround is to edit /etc/firestarter/firestarter.sh

Comment out the following block: 
#if [ "$MASK" = "" -a "$1" != "stop" ]; then
#echo "External network device $IF is not ready. Aborting.."
#exit 2
#fi

I made this change and Firestarter returned to normal operation

Version-Release number of selected component (if applicable):

How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
David Walser 2015-07-30 17:52:59 CEST

Assignee: bugsquad => mageia

Comment 1 macxi 2015-11-11 18:38:21 CET
I managed to run the firestarter in Mageia 5 without any additional configuration, only installing and running. Not understand why the previous error. I think it was giving error because I was pointing to the wrong network device. My mistake (PEBKAC). I've tested the Firestarter and it is working ok

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.