Firewall Management
Getting to Know Firewalld
Managing a firewall can be a hassle, but it’s worse to manage a breach because you didn’t have one.
Special Thanks: This article was made possible by support from Linux Professional Institute
A firewall is an important part of a security strategy, but it is only one component and is not a security panacea for reasons that will become clear later in the discussion. A host-based firewall protects the local system just as a network firewall protects an entire network or part of a network, such as a DMZ.
Firewalld is the default firewall installed on CentOS 7 and newer, Red Hat Enterprise Linux 7 and newer (RHEL), and Fedora 18 and newer. If you use a Red Hat-based distribution, then you probably have it already. If you use other distributions, it’s available via git and as a tarball from firewalld.org. Firewalld uses zones to define trust levels of network connections or interfaces. Zones are an advanced topic not covered in this article. There will be a future article that covers firewalld zones.
Firewalld Features
- IPv4 and IPv6 support
- Ethernet bridging
- IP sets
- Separate runtime and permanent configuration options
- No service or system restart required for configuration changes
- Complete D-Bus API
- Predefined Zone list
- Simple configuration options
- Flexible enough for complex zone rules
- Direct interface
- Simple log of denied packets
- Application whitelisting
- Automatic kernel module loading
- Puppet integration
- CLI and graphical configuration
NOTE: A firewall is a set of allow and deny rules that control packet flow to and from networks. A firewalld service is a combination of ports, protocols, modules, and destination addresses.
Troubleshooting firewalls
System administrators of all skill levels have wasted countless hours on troubleshooting a problem that ended up pointing to a firewall that has prevented remote access to a service. The term ‘remote’ is important. Firewalls don’t prevent access to local services. In other words, firewalls prevent access from remote systems across the network but not access from the local system itself. The point of a firewall is to deny everything from the outside except what you specifically allow in. Unfortunately, frustration with firewall rules often ends in the firewall being disabled by an otherwise well-meaning system administrator.
Troubleshooting firewall access is easy. In this example, you’ve just installed the Apache web server, NGINX, or some other web server of your choice onto a server system. You test from your workstation and you get a “This site can’t be reached” message in your browser. Here is the process of how to resolve the problem:
- Check the system’s process list to be sure the service is running.
- Test the service from the local system. Open a web browser (Firefox or Chrome, if you have a GUI or lynx, if not (lynx is a text-based web browser).
- Check to see if a firewall is running.
- Add a firewall rule to allow HTTP (TCP port 80) and HTTPS (TCP port 443) or whatever ports your web service uses. Reload the configuration to enable the rule.
- Test from a remote system again.
This same procedure works for any service accessed over the network. To illustrate the troubleshooting procedure above, the next section is a demonstration of setting up a web server and then remotely accessing it.
Setting up http and https access
Install a web server onto your system. For my Red Hat-based system, the process is simple to install the Apache web server.
$ sudo yum -y install httpd
Enable the web server to run at startup.
$ sudo systemctl enable httpd.service $ sudo systemctl list-unit-files | grep httpd httpd.service enabled
Start the httpd.service.
$ systemctl start httpd.service
Check that the httpd service is running.
$ ps -ef | grep httpd
root 1194 1 0 20:05 ? 00:00:00 /usr/sbin/httpd -DFOREGROUND apache 1199 1194 0 20:05 ? 00:00:00 /usr/sbin/httpd -DFOREGROUND apache 1200 1194 0 20:05 ? 00:00:00 /usr/sbin/httpd -DFOREGROUND apache 1201 1194 0 20:05 ? 00:00:00 /usr/sbin/httpd -DFOREGROUND apache 1202 1194 0 20:05 ? 00:00:00 /usr/sbin/httpd -DFOREGROUND apache 1203 1194 0 20:05 ? 00:00:00 /usr/sbin/httpd -DFOREGROUND
Test the web server locally using lynx or a graphical browser.
$ lynx http://localhost
Check that you can access the web server from a remote computer. It fails the test because the firewall is currently blocking all ports.
Check to see if a firewall is running.
$ sudo firewall-cmd -state running
To allow access from remote systems, you have to enable the ports configured for your web server. In this example, it is port 80. The --permanent switch adds the allowed port to the firewall’s permanent configuration.
$ sudo firewall-cmd --permanent --add-port=80/tcp success
Reload the firewall configuration.
$ sudo firewall-cmd -reload success
Check access again from your remote computer. You should see a web page appear in the browser.
Use this same procedure to configure other ports for your services. You can also add multiple ports before reloading the firewall’s configuration.
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
Canonical Releases Ubuntu 24.04
After a brief pause because of the XZ vulnerability, Ubuntu 24.04 is now available for install.
-
Linux Servers Targeted by Akira Ransomware
A group of bad actors who have already extorted $42 million have their sights set on the Linux platform.
-
TUXEDO Computers Unveils Linux Laptop Featuring AMD Ryzen CPU
This latest release is the first laptop to include the new CPU from Ryzen and Linux preinstalled.
-
XZ Gets the All-Clear
The back door xz vulnerability has been officially reverted for Fedora 40 and versions 38 and 39 were never affected.
-
Canonical Collaborates with Qualcomm on New Venture
This new joint effort is geared toward bringing Ubuntu and Ubuntu Core to Qualcomm-powered devices.
-
Kodi 21.0 Open-Source Entertainment Hub Released
After a year of development, the award-winning Kodi cross-platform, media center software is now available with many new additions and improvements.
-
Linux Usage Increases in Two Key Areas
If market share is your thing, you'll be happy to know that Linux is on the rise in two areas that, if they keep climbing, could have serious meaning for Linux's future.
-
Vulnerability Discovered in xz Libraries
An urgent alert for Fedora 40 has been posted and users should pay attention.
-
Canonical Bumps LTS Support to 12 years
If you're worried that your Ubuntu LTS release won't be supported long enough to last, Canonical has a surprise for you in the form of 12 years of security coverage.
-
Fedora 40 Beta Released Soon
With the official release of Fedora 40 coming in April, it's almost time to download the beta and see what's new.