Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Presumably you just want your firewall to start when you start the computer... in which case, add it to your startup programs (gnome) or to /etc/rc.local. But you are trying the other method in the firestarter docs...
did you remember to edit sudoers with
sudo visudo -f /etc/sudoers
and the line should be:
[my user name] ALL=NOPASSWD: /usr/sbin/firestarter
(spot the extra space)
Last edited by Simon Bridge; 09-20-2007 at 10:42 PM.
I understood that firestarter was a GUI for iptables ... I didn't know that installing firestarter also makes sure iptables runs an startup.
It is a wee bit puzzling that someone wants to be able to change the firewall rules unauthenticated. I'll have to hover around 'till OP leaves that machine unattended then swiftly change the rules to lock him out
I didn't know that installing firestarter also makes sure iptables runs an startup.
Well on Debian, iptables starts on boot by default. All Firestarter does is add new rules. I don't actually know whether that's the case on other distros.
After further thought: Actually, I guess I'm not even positive iptables starts by default. The first thing I always install is Firestarter, and I've never worried about it. On Debian, once Firestarter is installed and activated, the firewall is definitely activated upon boot.
I'm going to be installing a new system next week. Guess I'll check to see if iptables starts by default before I install Firestarter.
I wrote notes on this when I had Ubuntu (don't know where I found the information):
Go to System -> Preferences -> Sessions -> Startup Programs -> New
Type in Name: Firestarter
Type in Command: sudo firestarter --start-hidden
I have never added any triggers to start it, but during the boot process I see a message that the Firestarter firewall has been started, and after a fresh boot, ... # iptables -L -n includes the rules I have set up in Firestarter.
My primary firewall is the NAT one built into my router, but I have specifically left ports open thru it that I sometimes use; e.g. ports used by P2P programs. By default those ports are closed in Firestarter, and I only open them as necessary. I also have a Firestarter rule that all connections should be accepted from PCs behind my router.
One of the iptables rules enacted at boot (without ever activating the Firestarter GUI) is ...
ACCEPT all -- 192.168.123.0/24 0.0.0.0/0
In my system, from hoary on up, the rules are not brought up until I say so. Has never appeared upon ppp0 ore eth0 activating. Never found any default rules. How did you manage it?
Since you posted, I've been looking for hide or hair of a default Ubuntu firewall. I found ubuntu-firewall-cfg but not on my system.
It is (or was) a question that is asked when you setup either pppoe or firestarter.
If you search the /etc directory and its subdirectories for iptables, you should be able to find out how iptables are configured and started.
At this moment my Ubuntu system is down due to renovation of our kitchen, so no chance of checking.
For the record, on Debian, the base setup starts iptables with all ports open. When Firestarter is installed and initialized, without asking any permission, it starts up on every reboot with a "reasonable" set of rules including those specifically entered by you.