July Release Confetti
150+ New Courses, Hands‑On Labs, And
Interactive Learning Activities
Learn More

LiNUX Lab

Red Hat Security With FirewallD

We deploy the real environment, you take the scenario-based labs on us. Hands-on, from anywhere, at any time.

Time required: 3 Hours

Scope

Use the provided servers to configure and test firewalld rules.

Objectives

Learn how to start using the FirewallD tool within Red Hat Enterprise 7. Install and configure firewall rules, test and verify how the rules work between the two servers provided and your remote machine.

Overview

Learn how to start using the FirewallD tool within Red Hat Enterprise 7. Install and configure firewall rules, test and verify how the rules work between the two servers provided and your remote machine.

Before beginning this scenario, please perform the following steps once your system is provisioned:

A. Log into Lab Server 1 and change the password for the linuxacademy user.

B. Log into Lab Server 2 and change the password for the linuxacademy user.

 

Note: all tasks to be performed as the root user.  Or via sudo.

Scenarios

You have two new servers in your environment that are intended to have proprietary information on them. As a result, you will control access to various services on them using a firewall.

Provision the firewall on Server 1. Be sure that the 'iptables' service is not running and/or is masked. Start the firewall on Server 1 and verify it is running.

Install and start the Apache web server on Server 1. Using the 'elinks' text browser, browse to the 'localhost' site to verify it is serving the site on the default port. Check that your firewall's default zone is set to 'public'.

List the current rules for the default zone. Log into Server 2 and, using the 'elinks' text web browser, determine if the site on Server 1 is reachable.

Create a rule on Server 1 for the default zone that will allow TCP port 80 to be accessed from any incoming connection. Display the rules and then verify the rules has been applied by accessing Server 1 website from Server 2.

Finally, disable all port 80 TCP traffic on Server 1, making those rule changes permanent and verify that the rule has been applied by attempting to access the Server 1 website from Server 2.

Share our Labs
Start Your Free Trial

We have the longest and most in depth courses about cloud and engineering topics on the web. All of our training content is included with every membership.