Do I need to re-run Guarddog after every reboot?

M$ISBS · 03-30-2007, 05:32 PM

Do I need to re-run Guarddog after every reboot or does it store the settings through a reboot?

Also, is there an IPTables command (or switch) that would show me if Guarddog is actually working?

Thank You.

pljvaldez · 03-30-2007, 05:44 PM

iptables -L (list the iptables that have been loaded). If you see stuff, it's probably all okay. If everything is blank, then you need to re run guarddog.

M$ISBS · 04-01-2007, 05:44 AM

It looks like I do need to run it after every reboot. Thanks.

Lawrentium · 04-02-2007, 11:15 AM

Quote:

Originally Posted by M$ISBS

It looks like I do need to run it after every reboot. Thanks.

That shouldnt be necessary. I used Guarddog for a while, and was quite pleased with it. You should see something like Guarddog IPTables script initialized or something when you are booting Linux. If its not working right, you might want to try Firestarter. That's what I'm using now.

dracolich · 04-04-2007, 08:40 AM

I've been using Guarddog since I started using Linux. It creates a file called rc.firewall, which is just an iptables script, in the /etc directory. Make sure it's there and that it's executable. When you do run Guarddog and click ok or apply after making any changes watch the scrolling messages. If there are no errors you see something like this:

Quote:

Using iptables.
Resetting firewall rules.
Loading kernel modules.
Setting kernel parameters.
Configuring firewall rules.
Finished.

Note: Guarddog needs to be started with root permission to function properly.

tobyl · 04-09-2007, 03:47 PM

to expand on what dracolich said, guarddog installs by default in /etc/rc.firewall. Slackware by default looks for rc.firewall in /etc/rc.d/rc.firewall, and that is why you dont get it loaded at boot.

There is more than one way to fix this, see here:

http://www.linuxquestions.org/questi...d.php?t=534114

tobyl