Matt

Fantastic. Looks like I've finally got a good-working firewall. I will post a new thread regarding my iptables setup. Thanks again for all your help shanenin!

Hi shanenin. I've finally given up of Firestarter. Since Firestarter is just a frontend to iptables, I decided I would setup iptables myself and have that load on bootup. Here's what I did: iptables -F iptables -P INPUT DROP iptables -P FORWARD DROP iptables -P OUTPUT ACCEPT iptables -A INPUT -i lo -j ACCEPT iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT iptables-save > /etc/iptables.up.rules Then, I edited /etc/network/interfaces as follows: auto eth0 iface eth0 inet dhcp pre-up iptables-restore < /etc/iptables.up.rules(The last line was added) At the first cou

Happy birthday man!

Heya shanenin. I just got back home. Have you had a chance to mess around with it?

Hehe, well no worries. I'm in no big rush. Good luck with your move!

Thanks. I'm heading out of town again tonight, so after today, I won't be back again until Tuesday. If try anything else before I head out, I'll be sure to keep you posted.

hi shanenin. I'm wondering if there is a better way to go about following the steps I followed in my original post (editing sudoers or visudo). I'm also wondering if I should scrap Firestarter all together and go with something else that you might recommend? I'll wait for your reply. If this is a fight you think we can keep going at, then I'm all for it! If you think something else might be better, I can do that too. Thanks so much for the time an effort you've put into this thus far.

Yes it is

It did not start automatically again, and /etc/init.d/firestarter start did not start it either.

I followed your instructions using the 2nd start script that iccaros posted. This may seem silly, but would system -> Preferences ->Sessions and adding sudo /usr/sbin/firestarter as a startup do any good? Or would this not work because there won't be the correct sudo privileges? Edit: give me a sec, I'll try that command on reboot

shanenin, hold on a sec: Should I have done those commands on startup? I have manually started the firewall before entering those. Do you want me to do them again, without manually starting it?

matt@linux:~$ cat /etc/init.d/firestarter #!/bin/sh # # Init file for the Firestarter firewall # # chkconfig: 2345 11 92 # # description: Starts, stops, and lock the firewall # # Script Authors: # Tomas Junnonen <[email protected]> # Paul Drain <[email protected]> # # config: /etc/firestarter/configuration FS_CONTROL="/etc/firestarter/firestarter.sh" [ -x /usr/sbin/firestarter ] || exit 0 [ -x $FS_CONTROL ] || exit 0 [ -s /etc/firestarter/configuration ] || exit 0 RETVAL=0 start() { echo -n "Starting the Firestarter firewall: " $FS_CONTROL start > /dev/null RETVAL=$? if [ $RE

shanenin, that's what I'm saying. I just tried the method above, and it didn't seem to work. Since yours worked perfectly, perhaps I did something wrong?

*sigh* Well, on what we had before shanenin, my scans were at least showing up sometimes as the firewall functioning properly. At first try at this, shields up shows that it didn't work. There is a chance that I did something wrong I suppose. Is there something I can paste for you to check that it was done correctly?

That looks very cool isteve. Wanna pick me up one?

This is very strange.... I just ran hackerwatch.org and shields up scan after a new boot. This time, it is again telling me that my ports are closed, but insecure as opposed to when I start manually and scan. I don't get it at all. I did notice that if I manually run Firestarter, and then 'Exit' it, my port scan comes up as secure--so I know that it can run in the background. Maybe I haven't configured Firestarter correctly. Here's this, if that's of any help (before manually starting it): matt@linux:~$ ps -ef | grep firestarter matt 5768 5746 0 19:33 pts/0 00:00:00 grep firestarte

Hold up shanenin. I just rebooted again and went back to hackerwatch.org. This time, it is showing my ports as secure, and I did not manually start the firewall. It appears to be working! Is there a way I can see what processes/services/daemons (or whatever we call them in linux) are actively running to make sure the firewall is active?

matt@linux:~$ sudo /etc/init.d/firestarter Password: Firewall started I don't believe that it does run automatically. The reason for this is when I bot and go to hackerwatch.org and do a port scan, most of my ports return "Closed but visible". When I manually start the firewall, the scan returns all ports as "secure". Yes I do see your point. The script is obviously being executed, or that file would not have been created. The file even states that it was created by root, so we know that root privs are being used. Just to double check, here's my /etc/init.d/firestarter #!/bin/bash /etc/fi

itworked was created

It still didn't work

matt@linux:~$ ls -l /etc/rc2.d | grep fire lrwxrwxrwx 1 root root 21 2007-07-31 20:39 S20firestarter -> ../init.d/firestarter lrwxrwxrwx 1 root root 24 2007-08-02 09:27 S20firestarter.sh -> ../init.d/firestarter.sh

The site went down a because of issues with the server. Since then, Jeff has been in contact with the company that runs his dedicated server, and everything should be fixed now.

It does (after asking for a password). Is it running as a daemon when it does this? No GUI appears, but the firewall seems to function.

Here you go: matt@linux:~$ sudo cat /etc/init.d/firestarter.sh #!/bin/bash /etc/firestarter/firestarter.sh start #don't use sudo matt@linux:~$ ls -l /etc/init.d/firestarter.sh -rwx--x--x 1 root root 67 2007-08-07 11:06 /etc/init.d/firestarter.sh Small question: if I understand correctly, I was editing sudoers before because firestarter required a sudo pass to be started, and we were bypassing that. How are we attempting to bypass that now?

shanenin: the script didn't appear to work