Lab 10 mnjk

Introduction

Watch the video introduction

This lab assumes you have successfully set up DNS and email. If you had any issues with those labs, you should resolve them before attempting this lab, since you will be unable to properly test the tasks in this lab if those are not fully functional.

In this lab you will perform the following tasks:

• Configuring a [Firewall]
• Enabling 2nd interface
• Configuring [NAT]
• Setting up [DHCP]
• Enabling [Port Forwarding]

You will use the following commands:

• firewall-cmd
• [ifup]
• [echo]
• [ip]
• [ifconfig]
• [ping]

Lab Procedure

Prerequisites

1. Open an SSH console to your Linux system using the PuTTY software.
2. Login with your standard user account.
3. Have a browser window set to the webmin interface for your linux VM.

Configure a Firewall

NOTE: It is suggested that instead of managing a firewall directly using nftables tools (which would also require us to create a script to reload our rules each time the system is restarted) we use a firewall daemon program to manage it based on a set of rules we create and automatically setup the firewall based on those rules each time the system boots. There are many command line firewall management programs out there but for this lab we will use the firewalld package suggested by Debian.
1. Begin by installing the firewalld package on your system.
2. First, let's check to see if the firewall is now up and running using the following command:
firewall-cmd --state

The firewall has been pre-configured with a couple of rules in it to prevent us from getting locked out.

3. Let's see what those rules are by using this command:
firewall-cmd --list-all

By default all interfaces are in the public zone (this is set in the /etc/firewalld/firewalld.conf file).

Before we start working on rules for our firewall we should assign our outside interface to the external zone which is designed for NAT routing which we'll be setting up shortly.

4. We can do this with the command:
firewall-cmd --zone=external --add-interface=ens192

We can create custom zones or use pre-defined security zones which will speed up configuring the firewall. Learn more about the pre-defined zones in firewalld documentation.

5. Since we have changed zones on our interface let's check and see what rules we have started with. Let's see what those rules are:
firewall-cmd --zone=external --list-all

NOTE: You can also use the firewall-cmd --list-all-zones command to see a list of all available zones and their rules.

If you were watching carefully you may have noted that the dhcpv6-client service which was allowed in the public zone but is not allowed by default on the external zone.

6. In our case we want to allow DHCPv6 to operate on our outside interface so we can re-enable it with the following command:
firewall-cmd --zone=external --add-service="dhcpv6-client"
7. Check to see what other services can be allowed on an interface with:
firewall-cmd --get-services

If you check you will see that although you can connect with ssh (by default it's on the allowed service list you saw above) you can't connect to your webserver or Webmin anymore. Webmin is not a pre-defined service in the list we saw above so we could either set it up as a new service and then allow it or we could create a manual rule to allow the TCP traffic on port 10000 needed to access Webmin. In this case because the service only uses a single port and to see how manual rules can be created let's manually create a rule to allow access to TCP port 10000.

8. Do this by running this command:
firewall-cmd --zone=external --add-port=10000/tcp

You should now be able to access Webmin again.

9. Using either service rules or manual port rules create additional rules so that the other services on your VM are again accessible from the outside (such as from your home PC over the VPN).

HINT: Services we have setup so far include SSH, DNS, SMTP, IMAP, Samba, and HTTP.

Make sure to test and ensure they are all working again!

10. Once you are satisfied your firewall is running correctly you can use the following command to set these rules to automatically load each time the system is started.
firewall-cmd --runtime-to-permanent

Setup a 2nd NIC Interface

To start this lab we will need to configure a second network interface, named ens224 on our virtual machines. In our simulated setup our existing ens192 interface will be our WAN interface and ens224 will be our LAN interface which could be connected to a switch and then to multiple allow other computers which will connect to the Internet through our server.

1. Open /etc/network/interfaces with your favorite text editor.
• Go to the bottom of the file.
• Add the following to configure the second interface with a static IP of 192.168.1.1/24:

auto ens224
iface ens224 inet static
	address 192.168.1.1
	netmask 255.255.255.0

NOTE: As this is a LAN only interface, we do not need to define a gateway for the server VM, as the server VM itself will be the gateway for this network.

2. Once this is done, save the file
3. Run the following command to enable the new interface.
ifup ens224
4. Verify the second interface is up and running with the correct IP address

Enable Routing

1. Now we will need to enable NAT so we can route LAN traffic to the Internet and responding Internet traffic back to our LAN interface.
2. In your console, you will need to edit /etc/sysctl.conf. This file is used to change and tweak multiple system variables. Scroll down until you find the following:

   # Uncomment the next line to enable packet forwarding for IPv4
   #net.ipv4.ip_forward=1
   

3. Follow the instructions in the file to enable packet forwarding in the kernel. When you are done, save the file.
4. Changes to the sysctl.conf file require a reboot, but most can be set without a reboot by echoing response codes to "files" in /proc. We will get into that more in a later chapter, but for now run the following command to enable ip_forwarding without rebooting the machine: echo 1 > /proc/sys/net/ipv4/ip_forward
• Note: If you are receiving an error when trying to run that command it's likely that the user you are running it as does not have permission to modify the /proc/sys/net/ipv4/ip_forward file (check the permissions by using ls). Read this similar question for more details and possible solutions.

Setup a DHCP Server

1. To setup a DHCP server, we will first need to install the required software. In your SSH console use your favorite package manager to install the isc-dhcp-server package.
2. After you install the package you may get a warning about isc-dhcp-server being unable to start. This is normal as we have yet to define the interface and settings we want used.
3. Now back in Webmin, select the Refresh Modules option. After it is done, go to Servers, then DHCP Server.
4. Before we define our DHCP range, we need to set our listening interface. Click on the Edit Network Interface option, and select ens224 and press save.
5. Now under Subnets and Shared Networks, select Add a new subnet. Use the following settings:

   Subnet description: LAN DHCP Range
   Network Address: 192.168.1.0
   Netmask: 255.255.255.0
   Address Ranges: 192.168.1.100-192.168.1.254

6. When you are done, press Create. Now, click on the network you just created to review the settings, then press Edit Client Options at the bottom.
7. From here we will setup the default gateway and DNS servers for the clients to use. Under Default Routers, set the option to 192.168.1.1 and under DNS servers, set it to 192.168.1.1 as well. Notice how we are setting these options to the IP of ens224 that we setup. This is because our Linux VM will act as the router and DNS for our clients as well.
8. When you are done, press save, and then on the Edit Subnet page, press save again.
9. Now that you are back on the DHCP server page, press the Start Server button. If all goes good, the button should change to "Stop Server". If this does not happen, then the server was unable start. If that happens, re-check your DHCP server configurations to make sure everything is correct.

Enabling NAT and Firewall Rules for the LAN

Now we will use firewalld to setup NAT so that we can use private addresses on our internal LAN but still have access to the public Internet. First, let's set our ens224 interface (LAN) to be in the internal zone with the firewall-cmd --zone=internal --add-interface=ens224 command.

You should now take a minute to all all of the same services and ports on the internal network that you have allowed on the external network. In other words, make sure that Webmin, Samba, DNS, etc. are also allowed on the internal zone.

In order to activate NAT you need to turn on the "masquerade" feature on your outside interface. This is probably already done if you correctly assigned your outside interface to the pre-defined external zone (it's one of the features of that zone) but you can do this manually as well in case you setup a custom zone by running the firewall-cmd --add-masquerade --zone=external command.

While routing and NAT should be working for hosts on your LAN interface now they probably still can't get an IP address! Just like all the other services being blocked by the firewall DHCP is also blocked unless you specifically allow it. To do this run the firewall-cmd --add-service=dhcp --zone=internal command.

Once you are satisfied your firewall is running correctly you can use the firewall-cmd --runtime-to-permanent command to set these rules to automatically load each time the system is started.

Setup a 2nd VM as a LAN Host

1. Now we are going to setup a 2nd VM on the VMware server so we can have a client to connect to the LAN network segment we just created. For this though, we will be using Linux Mint instead of Debian so we have a graphical user interface to help us with testing.
2. You'll need to make a Netlab reservation to work with your Mint system's GUI so go ahead and do that, enter the lab on Netlab, and click the "Linux Desktop" tab to access your Mint machine.
3. The VM should be booting from a Linux Mint virtual CD image. Get Linux Mint installed using the link on the desktop, installation settings are not critical as we'll be using the system primarily to explore a Linux GUI and to test web browsing capability from our private network.
   • NOTE: By default Linux Mint will boot into a "Live CD" environment where you can use the system without installing. However, the Live CD environment is much slower and memory limited compared with a full installation to the hard drive so be sure to start an installation and reboot into the installed copy instead of from the Live CD. You will know you're working from an installed copy if you are prompted for your username and password when logging in and don't see a link on the desktop to Install Linux Mint anymore.
4. Once you have Linux Mint installed, reboot the machine and login. Hopefully the machine is able to connect to the Internet through your Debian server which is acting as a DHCP server and router (see the topology diagram tab in Netlab to see a diagram of how they are connected).
5. Press the Menu icon in the lower left corner, and enter "Terminal". Then, open the terminal application.
6. You now have a shell on the system. From here, use ip address show to check your network settings. Notice how you have a IP from the DHCP pool we created earlier. Now try pinging 172.17.50.1. Are you able to ping? If so, NAT is working properly on your network because the 172.17.50.0/24 network is outside of the LAN segment this machine is attached to (192.168.1.0/24).
   • NOTE: Notice how some Linux distributions like Mint haven't switched from the old naming of network interfaces with eth to the new ens style. You can also try using the older ifconfig way of checking the IP address and compare the output to the new ip address show method which we have been using so far in Debian.
7. Now run ping google.com. If you are able to ping, this shows that not only is NAT working, but DNS resolving as well.
8. Open a web browser on the system (you can use a graphical browser this time since you have a GUI) and test browsing to a few websites.
9. At this point we have a fully functional LAN environment.
10. In order to allow automatic safe shutdown of your Linux Mint system and improve speed/efficiency use the package manager to install the open-vm-tools-desktop package. This provides better drivers and integration between the vmWare host which is running your Linux Mint virtual machine and the virtual machine itself.
11. Spend a few more minutes exploring the functionality of the Linux GUI and desktop.

Port Forwarding and Firewalling

1. Now we are going to enable port forwarding to our VM. This will allow you to access the 2nd VM from the ITC network and VPN.
2. Because we are already using port 22 on our outside interface to provide SSH access to our main Debian system we need to use a different port to access the Mint system. Instead of changing the port number in the SSH server software on Mint we can have our firewall do it at the same time the NAT masquerading is occurring. Set up a rule by running the firewall-cmd --add-forward-port=port=2222:proto=tcp:toport=22:toaddr=192.168.1.100 --zone=external command. Note that this rule is a little unstable because it forwards the port to 192.168.1.100 which is currently the IP of our Mint system (if yours has a different IP you should change it in the command) but because that system gets an IP from DHCP it is subject to change which would break the rule. Therefore, if we wanted this to be stable in the long term, we would want to set up a static IP on any machines we were forwarding ports to.
3. From a computer on the ITC network, such as one connected to the VPN, try to SSH to port 2222 on the outside (17.17.50.xx) IP address of your Debian system. If everything was setup successfully, you should be able to sign into the Mint VM based on the port forwarding rule we have put in place.
4. Once you are satisfied your firewall is running correctly you can use the firewall-cmd --runtime-to-permanent command to set these rules to automatically load each time the system is started.
5. When you are done testing this section of the lab please power off your new Linux Mint VM as these require far more resources to run than the Debian VMs on our servers.