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.
After running lilo and a reboot, I ran the newly named myfwconf. At the ncurses window, I selected yes to begin. The highlighted yes turned to no. The only way out was to select no.. I gotta reread what SCerovec did.
After running lilo and a reboot, I ran the newly named myfwconf. At the ncurses window, I selected yes to begin. The highlighted yes turned to no. The only way out was to select no.. I gotta reread what SCerovec did.
Yes it is what it is - a very basic, somewhat customizable, firewall.
Nothing to write home about (as of yet) but the point is to get it to life first, then only we might (or not) add somewhat more fancy like the trapit destination or some other of the many Linux kernel iptables specialties
I have been using Alien Bob's Easy Firewall Generator since Slack 13.0 and it has always worked nicely. After generating a basic firewall you can always tune it according to your needs.
I've been using this script as well: something like this script, at the end of setup, wouldn't hurt... it's the first thing I usually do anyways. I think this script could be updated to also handle ipv6 connections--since it doesn't, I have been disabling ipv6, because I don't seem to need it.
It's easy enough to create different configurations and have /etc/rc.d/rc.firewall.home vs /etc/rc.d/rc.firewall.cafe. /etc/rc.d/rc.firewall could use arp to compare mac of router to see if it matches home router, and then execute the home version... and if no match, execute the cafe version, thereby having "zones". Of course, to use arp, the network is usually up... /etc/rc.d/rc.firewall could call dhcpcd -G (does not set default routes) so as to deterimine mac address of router and set appropriate firewall. The route would be set when running NetworkManager afterwords.
IMHO, answering some basic firewall questions at the end of setup would be a fine addition to slackware: advanced users would and should change it afterwords to whatever they prefer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.