Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I've installed Suse 8.2 and run Yast to configure the firewall.
The machine is leasing an IP on eth1 from my cable modem and eth0 is my internal interface that is up routing no problem (currently using VNC to log into firewall box internally).
Yast shows the firewall as setup with the external interface as eth1 and the internal interface as eth0.
I'm planning on running a web server on this so I've enabled http and https as well as ssh as available services then on the final config screen I've selected only to forward packets and do masquerading then to log only critical dropped and accepted packets.
It will "start the service" however I'm unable to route to the Internet from my internal machines. Public DNS will not resolve nor will public IP addresses.
Moving from Redhat to Suse I've noticed some differences. There is no rc.firewall in the rc.d directory, I've tried to run iptables -L forward to give some sort of idea but it comes back that Table does not exist (do you need to insmod?)
I'm lost. I've tried to manually edit the /etc/SuSEfirewall2_final but got lost in that document too.
firstly, check if you are using iptables or ipchains. that would explain why iptables appears to be dead.
secondly, check if you are using a firewall config tool like shorewall, that would simplify it for us to solve your problem.
I'm using the firewall control center in Yast. It's not the shorewall labeling that RedHat uses and I do not recall how to determine if iptables or ipchains is being used. I've tried both iptables -L and ipchains -L and neither come back with a valid response.