Exactly the same problem as ChrisLasher earlier. WIFI not up when firestarter script called - dangerous :(
My solution, edit /etc/firestarter .. # *** Commented out by me otherwise firestarter wont start due to wifi not started *** #if [ "$MASK" = "" -a "$1" != "stop" ]; then # echo "External network device $IF is not ready. Aborting.." # exit 2 #fi And now firestarter works every time. OK this is a sincere question - I am no security expert - why does firestarter need to check to see if the eth? port is up before applying the iptable rules ? It appears that when firestarter starts all non defined ports are blocked so if firestarter IS mis configured network issues would alert the user. This has got to be better than silently failing and leaving the user vulnerable. -- Firestarter init fails on system boot when NetworkManager is used https://bugs.launchpad.net/bugs/42759 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
