On Sun, Apr 23, 2006 at 11:38:25 +0200, Alexander Sack wrote:
> On Sat, Apr 22, 2006 at 08:00:37PM -0700, lmyho wrote:
> >
> > But it didn't work, the firestarter still doesn't load when the system boot
> > and jack
> > logedin.
> >
> > Then I changed the line in sudoers to: jack ALL=NOPASSWD:
> > /etc/init.d/firestarter
> > start, and changed the line in GNOME Preferences->Sessions->Startup
> > Programs to:
> > sudo /etc/init.d/firestarter start, too.
> >
> > But the firestarter still doesn't auto start at the system boot!
> >
>
> Maybe consider this:
>
> firestarter consists of two parts. The first is the gui which is used
> to administer iptables firewall rules. The second is the init script which
> takes care that your current firewall rules are loaded at system
> startup. Thus, though there is no gui running your firewall is
> still effective, so you probably don't need firestarter to be started
> automatically, but just if you want to change your firewall rules.
If you are unsure about whether the firewall is running without the GUI,
you can check it with the following command in a Gnome terminal or on
the console (as root):
iptables -L
If my firewall is deactivated I see this:
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
If my firewall is active, I get 2-3 screens of rules scrolling by which
DROP or REJECT a lot of packets. (iptables is the direct command to
access the modules in the kernel which handle the firewalling,
firestarter is a convenient means for you to set these somewhat
complicated rules according to your needs.)
--
Regards,
Florian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
