I suppose that wasn't the most helpful contribution to the bug above, sorry about that--let me give a little more info. This is with ipw3945 (Intel ProWireless 3945 ABG builtin module) seen as eth1. Happens on WEP, WPA, or non-secure networks. Problem occurs because wireless is not "up". Firstarter fails to activate the tables once NetworkManager has established a connection, though. I have to manually restart the firstarter daemon, or load firestarter. Note that if I put gksudo firestarter in my sessions for startup app, it fails because it can't find device eth1 (because NM hasn't gotten the chance to establish connection with the network). If, after establishing a connection with the network, I log back in, firestarter starts with the session, because the network connection has been established, and thus eth1 already "exists". Hope this helps more. I love Firestarter and will continue to use it, even with this nuissance, but it would be great if it would "just work" with NM.
-- Firestarter init fails on system boot when NetworkManager is used https://launchpad.net/bugs/42759 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
