DebianThis forum is for the discussion of Debian Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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.
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.
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:
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
/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.
Looking at the scripts, I still don't get why firestarter does not start at boot.
According to the README in rc2.d
The scripts in this directory are executed each time the system enters
The scripts are all symbolic links whose targets are located in
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.
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.
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.
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.
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.