Firestarter does'nt start automatically

micder · 05-08-2007, 01:07 PM

Just installed Etch with KDE desktop.
One of the first things was installing a firewall; used firestarter.
Started Firestarter as root and checked at Shields Up: OK.
Found lots of documentation on installation of non-free apps such as NVidia.
(My GeForce 6200 TurboCache does not work with nv).
I had a complete desktop in a short time.
And Etch is very fast !!

However info on Firestarter does not make sense (for me).
I have to start Firestarter manually with sudo firestarter after logging in.
Why does Firestarter not start during boot?
firestarter in /etc/init.d is executable.

nomb · 05-08-2007, 01:12 PM

You have to add the sudo firestarter command to your rc.local I think it is. I tried firestarter on debian and had a few issues with it. As an alternative try something like this:

http://www.nombyte.com/?q=node/5

rickh · 05-08-2007, 01:21 PM

It's probably running. It just doesn't open a desktop window.

Try this:
$ pidof firestarter

If that returns a number, it's running.

micder · 05-08-2007, 01:43 PM

It does not start during boot, even after adding sudo firestarter to rc.local.
Up to now only sudo firestarter in a konsole did start the firewall.
BTW checked that with shields up.

There's a lot of scripts in /etc/init.d that get started at the right time.
It still puzzles me that firestarter is not triggered.
Did not have that problem with Mepis.

Thx for the reactions :-)

nomb · 05-08-2007, 01:51 PM

using sudo to start firestarter is how it says to do it in the documentation. Make sure that firestarter is one of the programs you can use sudo for and if not add it. And also in the rc.local file you need to put the full path. /sbin/firestarter or whatever it is for you. As an alternative take a look at the link I gave you. especially the init scripts. You could take that script and convert it for firestarter if you really want to.

rickh · 05-08-2007, 02:31 PM

My response in #3 was wrong. The only way "pidof firestarter" will return a process number is if the GUI is running. But once you have it set up, it will probably start on boot.

My setup depends on a NAT firewall in the router which has several ports that I regularly use left open. Those ports are defended by Firestarter unless I use Firestarter to open them. I also have a policy defined in Firestarter that allows connections from any "local" PC attached to the router.

I just rebooted, and have not opened the Firestarter GUI, but I know it's working because # iptables -L -n includes the line:

ACCEPT 0 -- 192.168.123.0/24 0.0.0.0/0

cgjones · 05-08-2007, 04:14 PM

If you are just trying to get the Firestarter GUI to start, check out this link.

micder · 05-09-2007, 05:22 AM

Thank you all for your suggestions.
Understand now that I can start the firewall via KDE autostart.
That's one way to start automatically.
Had a look at the README in /etc/init.d

Quote:

/etc/init.d/*.sh scripts must conform to the rules for sh scripts as
spelled out in the Debian policy section entitled "Scripts" (§10.4).

It seems that firestarter does not comply:
I can't find a link in /etc/rcS.d.

Installed guarddog and there is a link in /etc/rcS.d.
I did not find the required /etc/rc.firewall as said in the guarddog documentation.
So did that myself and now the firewall is started automatically at boot.

cheers

rickh · 05-09-2007, 10:09 AM

Quote:

I can't find a link in /etc/rcS.d.

How about rc2.d ... That's where mine is.

micder · 05-09-2007, 02:20 PM

Ya, rickh, its (firestarter) in my rc2.d too.

Pls enlighten me:

Looking at the scripts, I still don't get why firestarter does not start at boot.
According to the README in rc2.d

Code:

The scripts in this directory are executed each time the system enters
this runlevel.

The scripts are all symbolic links whose targets are located in
/etc/init.d/ .

The starter link for firestarter resides in rc2.d and the one for Guarddog in rcS.d.
I'm not familiar with the (for me) complicated initialization of Debian.
Anyhow complicated compared with Slackware.

rickh · 05-09-2007, 03:12 PM

Quote:

complicated initialization of Debian

It's not complicated. It's just new to you. I still maintain that Firestarter is starting when you boot. It's just not opening a gui. There is no reason it should. Open the gui, and add a very specific rule, like ... allow inbound connections on port 6001 from anyone. Reboot, and run # iptables -L -n and you will see the rule in place.

If what you want is a gui open on boot, that's a different issue.

nomb · 05-09-2007, 03:21 PM

Thinking back what I did was add a sudo /sbin/firestarter to gnome's start program each session option. But again, that made the gui start. What rickh said makes a lot of sense so you should definately add a rule and see if it is in you chain when you reboot.

micder · 05-10-2007, 08:15 AM

OK, removed guarddog and reinstalled Firestarter.
See something like firestarter starting..? flashing along during boot.
Checking at Shields up after boot: all common ports closed except 113 Ident.
I then do sudo firestarter, go back to Shields up and see that all ports are Stealth.

nomb · 05-10-2007, 08:29 AM

now u can add that to your list of programs to start when your session does and be done with it.

micder · 05-11-2007, 06:06 AM

nomb said:

Quote:

now u can add that to your list of programs to start when your session does and be done with it.

I could do that, but my firewall will start only when starting X.
Or do I miss something?
Guarddog is started before X is started.
It's maybe a small difference, but I thought that the firewall should be up asap.
Thank you all for your patience and help.

cheers