Guarddog - rc.firewall not stored in rc.d directory
 

After installing Guarddog, I wanted to veiw the output.. I couldn't find it where I thought it belonged - in the /etc/rc.d/ directory.

Instead it was simply in the /etc/ directory. Wouldn't this render it ineffective? I thought iptables looked for the file in the rc.d directory.

Reboot your machine and run iptables -L -n If you don't get the expected output, they don't work.

Sounds like your using slackware. I don't think that iptables looks for anything in /etc/rc.d. rc.iptables (or whatever the script is called) is a script the should be started at boot and for that reason should be in /etc/rc.d

I am using Slack.. I rebooted a couple of times and checked the syslog (only after copying the rc.firewall file from /etc/ to /etc/rc.d/ and there are logs or dropped packets in there - so one would assume on some level it is working.. I just dont know from which file.

I ran the above command and got some references to different chains. If I could remeber how to make the output go page by page (forgot the bash command) I could better tell what is doing what. But I dont know enough to track down which file is running at boot.

Now I have gone and removed the rc.firewall file from /etc/rc.d/ and rerun the iptables -L -n command and there are no chains defined. It basically shows an open door.. I think I might have to uninstall Guarddog and go back into the ./configure and see if there aren't some path settings I can set before the install.

I've been using Guarddog on my Slackware machines for a long time. It does indeed install the rc.firewall and rc.firewall~ files to /etc, not /etc/rc.d. I've never had any problems with them being there. As long as it's executable it should function properly.

My final solution was this... Uninstall guarddog...Install Dropline Gnome... Install Firestarter... Play with configuration a little bit... Firewall up and running.. Took me a long time, but it seems I have exactly what I wanted without all the fuss..
Thanks.