SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The Linux kernel has a built-in firewall, so it comes with every distribution. For Slackware, it is not turned on by default.
The easiest way to do it is via Guarddog, available on linuxpackages.net. Otherwise, make /etc/rc.d/rc.firewall executable and put your iptables commands in there.
First, i tried to turn on the firewall manually by going to [b]/etc/rc.d[b] but there was no rc.firewall script there. So I searched for it and saw that it was not even present in my hdd.
So I tried the second option.. downloaded guarddog, installed it and tried to run it. But it says "Failed to connect to X server" and refuses to start. Any suggestions?
The "failed to connect to X server" may be due to the fact that you started no X server before. Easiest thing is to run it from KDE, GNOME or whatever you are using. You will also have to create a symlink (ln -s) from source "/etc/rc.firewall" (created by guarddog) to "/etc/rc.d/rc.firewall" (where slack expects it).
First of all the error message I get is "guarddog : cannot connect to X server". I get this same message in GNOME, KDE and XFCE. I have also tried downloading and installing another firewall called kmyfirewall. It also gives the same error message "kmyfirewall: cannot connect to X server"
I think this is some wierd library initialization error or something... I read somewhere that u need some library installed...but could not get that page now... may be this has something to do with that problem.
I tried going thru the manuals of Iptables but ended up totally confused...what to do in Slack?
Iptables is complex; I think you should concentrate on getting guarddog operational, otherwise you'll end up with no firewall at all. For me, it works OK with Slack10, no X tweaking whatsoever.
First of all the error message I get is "guarddog : cannot connect to X server". I get this same message in GNOME, KDE and XFCE. I have also tried downloading and installing another firewall called kmyfirewall. It also gives the same error message "kmyfirewall: cannot connect to X server"
Hello,
If you are logged into X (KDE, Gnome, etc.) as a regular user, and you try to run an X app as root from a terminal, the root app will not be able to connect to the X server. (Although I seem to remember a command to launch an app using the current X session. Hmm?)
If you are logged into X (KDE, Gnome, etc.) as a regular user, and you try to run an X app as root from a terminal, the root app will not be able to connect to the X server. (Although I seem to remember a command to launch an app using the current X session. Hmm?)
Jim
This was my problem And such a simple one...right.
I also have used a command to share the X session but I forgot.
Okay...after installing using guarddog and copying that file to /etc/rc.d/ , what else to do ? how to make that script execute at startup??? Also...if I just execute the script, will the firewall start, or should I do something else...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.