Reallylinux.com 2012 Logo   Website for Beginning Linux Users
Read in 133 countries by over 600,000 users.


  Main Menu
Linux Help
Favorite Links
Our Community

  Site Search
Search our exclusive articles:


  What's Hot
Welcome to one of the leading websites for Linux beginners!

www.reallylinux.com       print

Personal Firewall Configuration for Fedora Mandrake & SuSe - www.reallylinux.com      

Personal Firewall Configuration for Beginners
By Mark Rais, author of Linux for the Rest of Us 2nd Ed. and senior editor for reallylinux.com.

Read our other Firewall articles including:
Beginner Business Firewall Use
Starting With a Firewall Server


When Linus and a handful of other passionate software engineers began to write the core of what is today “Linux” they understood the implications of security for networked systems. Linux is fundamentally, at its core, an operating system devised for network use and thereby includes a far wider and more effective array of security features than most people know of or care to communicate.

It may explain why a significant number of companies are using Linux for their infrastructure servers. It should also be an encouragement to you as a Linux user that many security goodies are already available, and in most cases are already running on your Linux PC!

Firewall and network security features are, in almost all newer flavors, integrated and operational as soon as you install Linux. However, there are times when you may need to adjust the firewall settings. For the most part, this would only need to be done if you choose to use your Linux PC as a server, allowing access by other networked PCs.

The number one reason people change existing firewall settings is to allow httpd (web browser) connections by other computers so they can view web pages from your Linux server.

This brief article shows the basics of how to change your firewall settings for Fedora, Mandrake, and SuSe to allow httpd connections by other networked systems.

The examples given assume that you are setting up a simple intranet server. For a more complex setup where the Linux server handles both internal and external requests, please look at our business firewall article. For instance never allow Telnet connections for an Internet server. Instead only allow SSH.


BASIC Fedora Firewall Configuration

Without a doubt, this is an easy process using the Fedora security tool. From the Fedora main menu, choose System Settings, then Security Level.

Or, if you prefer, just type the following command into a terminal:
system-config-securitylevel

Notice that by default no WWW (http) access is permitted to your server. Select the services you want to allow on your server and press OK.

The screen shot below shows the usual settings for an intranet or internal server where no major security threats exist.

Allowing direct telnet and FTP requests may not be a wise choice if your server also connects to the internet. In such an instance granting only WWW and SSH would be reasonably sufficient and secure.

Once the changes have been save, reboot the server to be absolutely certain that the new settings are configured properly.


BASIC Mandrake Firewall Configuration

Begin by accessing the Mandrake Control Center. From your main menu, select System, then Configuration, and Configure your computer.

If you prefer, you can also access this by simply typing the following command into the Konsole: drakconf

From the Control Center menu, choose the Security icon.

Next choose the Firewall icon. This will start the Firewall utility. On most Mandrake systems, the firewall is disabled by default.

The sample below gives an idea what are the typical services allowed for an intranet server. You would usually only allow web and SSH for an internet server. To make firewall changes, first ensure that the option labeled Everything is unselected.

You will also be allowed to choose which network device is protected by the firewall, such as your DSL modem connection (ppp+) or your network card (eth0).

Finally, you may be asked to install the shorewall package from the CD if you didn’t include it in your initial install. Press OK to let it install.

Now I recommend you do a reboot to ensure all the changes are made.


BASIC SuSe Firewall Configuration

As with almost all configuration, the useful YaST tool also includes a very easy wizard for updating your firewall settings. From the main menu, choose System, then Configuration, then YaST. You can also get to it quickly, so long as you’re logged on as root, by typing the command: yast

From the YaST main menu, choose Security and then Users. You will see an option to the right labeled Firewall. Select Firewall and then choose to reconfigure.

You’re going to see a strange, rather complex message appear. The message is irrelevant because there is only one good reason to modify your personal firewall and that is to reconfiguring it for broader server use, which is what we want to do!

Therefore, simply click Continue and then the Next button, until you arrive at the screen where you can choose the specific services you plan to allow access to your server.

Here, be sure to select the needed services to allow for server use. The obvious ones that most intranet Linux servers require are noted with circles.

Now, click Next and then be sure to unselect the Protect from Internal Network option. This is very important!

This will make your Linux server accessible for intranet server use to other LAN (local area network) PCs. Press the Next button twice and then press the Continue button. Your basic Linux firewall configuration is now complete!




For the complete list of Linux articles, please visit our HELP PAGE.

Who Are We?     -    Legal Information.     -    Privacy Policy.


latest release
1999 - 2012 Reallylinux.com   All Rights Reserved.

Penguin images special thanks to the artistry of Larry Ewing.

Some graphics icons are free courteously of: Icons by: FastIcon.com


Linux is a registered trademark of Linus Torvalds.
All other trademarks
and registered trademarks on this entire web site are owned by their respective companies.
This site is not related or affiliated with any other sites.