OPS335 Lab 2b
Contents
OBJECTIVE & PREPARATION
In Lab 2a, we set the firewall rules for your host machine. In this lab, we will create firewall rules for our virtual machines within our virtual private network. This lab will also apply "best practices" and "troubleshooting techniques" using iptables.
Online Resources
INVESTIGATION 1: CUSTOM IPTABLES RULES ON A VM
We will now set iptables rules for your vm1 machine.
Perform the following Steps:
- Start your host machine, and launch your vm1 machine.
- Login to your root account on your vm1 machine.
- Issue a command (like you did in lab2a) to copy your default iptables rules to the file pathname:
/etc/sysconfig/iptables.original - Issue an iptables command to set the policy to disable all forwarding traffic, and remove the rule that is rejecting it.
- Next, set the default policy to drop all inbound traffic, and remove the rule that is rejecting traffic.
- Issue an iptables command to list rules for verification.
The remaining tasks will relate to that same inbound traffic chain: - Issue an iptables command to delete the default ssh rule.
- Issue an iptables command to add a rule that allows ssh traffic (i.e. tcp packets with destination port 22) that originates from any machine within your virtual network.
- Issue an iptables command to delete the default icmp rule.
- Issue an iptables command to allow icmp traffic from addresses in your virtual network.
- Test that your machines can still use ping and ssh to communicate with each other.
- Save your rules in the location that iptables will automatically read from when it starts.
- Reboot your machine and check that the new rules are being applied. If they are not, resolve this issue before moving on.
- Now copy the file to your other VMs and make it apply to them when they boot as well.
- Reboot each machine and make sure this works before you move on.
Record your observations in this section on your OPS335 lab log-book
INVESTIGATION 2: IPTABLES TROUBLESHOOTING CHECKLIST
By now, you have probably discovered that a simple mistake in your iptables rules can have very serious and unexpected consequences for not only your services, but the network connectivity in general. There is a general process (checklist) that you can following to help troubleshoot iptables in order to fix the problem.
Refer to the following IPTABLES Troubleshooting Checklist:
| Step | Procedure | Explanation |
|---|---|---|
| 1 | Test Network Connectivity | You can use the steps in lab 1 as a guide, but keep in mind the firewall may be blocking pings and DNS requests. |
| 2 | Verify Service is Running & listening on the correct interfaces | You should learn to read the output of ss -atnp and ss -aunp to complement the systemctl status command. |
| 3 | List your iptables Rules & Perform a "Walk-Thru" | For many decades, when troubleshooting programs that don't run properly, programmers will resort to reading their "source-code" line-by-line and pretend they are the computer to perform the operation. The programmer "walks-through" the code to force them to think like a computer in order to spot and fix subtle problems. Therefore, you can follow a packet's path as you understand it should follow. Keep in mind the diagram from the lecture last week. What chain applies first on which machine? What's the first rule that matches the packet? What happens if no rules match the packet? Don't forget that even if you're tracing the path of outgoing traffic - the INPUT chain on your machine still applies (for the response that comes back to your request). |
| 4 | Use the log target to list unexpected traffic | Add a final rule to your input chain to log all traffic. Any traffic you are allowing will have already been accepted and will not reach this rule, so you will start a log of all the packets you are not allowing. Observing the logs while you attempt to use the service that is not being allowed will show you the type of traffic you need to allow. |
| 5 | Verify Network Connectivity by Deleting iptables Rules | As a last resort, if you have no idea what's going on and need to confirm that you're still sane - clear all the iptables rules and check your configuration then. Keep in mind that the iptables -F command will delete all your rules but will not set the default policies to ACCEPT. This will tell you for sure whether your problem was (or was not) caused by iptables. If you do this - have a ready way to restore the rules you just deleted. Restarting the iptables service is usually a good start and a shell script to add your custom rules is a reasonable next step. |
At this point, you should be able to understand any iptables rules you experience in this course, including the default ones in CentOS. If you see a iptables rule that you don't understand, you can delete it and see what happens. But if you simply delete this rule, take the time to figure out what that rule did and why you needed to delete it. It was likely there for a purpose (other than to drive you crazy).
Record the troubleshooting checklist in your OPS335 lab log-book
INVESTIGATION 3: HANDS-ON IPTABLES TROUBLESHOOTING
You will now get additional practice on troubleshooting iptables by downloading a running a shell script that will create iptables rules that will cause problems. You will then need to use tools and procedures (IPTABLES Troubleshooting Checklist) to determine the cause of the problem and fix that problem.
Perform the following steps on your HOST:
- Download and run the following script: http://scs.senecacollege.ca/~andrew.smith/ops335/lab_practice_iptables.sh
This will display a menu of exercises. You can choose any of the items in order, but you should attempt all of them. The script will first reset the firewall settings to CentOS defaults and then make some modifications from those defaults. - Troubleshoot and fix the problem as you would on a real server. The point of the exercises is for you to find the problem using regular troubleshooting tools, not to reverse-engineer the shell script.
- Finish the exercises, and record any information you feel you'll need to remember to solve problems like this in the future (e.g. in an assignment and/or in a practical test).
You MUST perform a full backup of ALL of your VMs whenever you complete your OPS335 labs or when working on your OPS335 assignments. You should be using the dump command, and you should use the Bash shell script that you were adviced to create in order to backup all of your VMs.
Record your observations in this section on your OPS335 lab log-book
COMPLETING THE LAB
In completing this lab you have gained further practice using iptables. Each of your machines should now be protected by a custom firewall that we will continue to build on throughout the course. You have also gained experience troubleshooting iptables and determining what rules might need to be changed to allow desired traffic (or block undesired traffic).
Depending on your professor you will either be asked to submit the lab in class, or online. Follow the appropriate set of instructions below.
Online Submission (Peter Callaghan's Classes only)
Follow the instructions for lab 2b on moodle.
In Class Submission
Arrange evidence (command output) for each of these items on your screen, then ask your instructor to review them and sign off on the lab's completion:
- ✓List iptables rules for ALL machines.
- ✓Prove that you can ping and ssh from your host machines to all of your vms.
- ✓Download the labcheck2b.bash checking bash shell script by issuing the command:
wget http://matrix.senecac.on.ca/~peter.callaghan/files/OPS335/labcheck2b.bash
set execute permission and run the shell script on your host machine.- For Peter's classes, follow his Online Submission instructions in Moodle.
- For Murray's classes, run command (piping to the more command) and show output to instructor.
- ✓Completed Lab2 log-book notes.
EXPLORATION QUESTIONS
- List 3 separate techniques that you used to help troubleshoot to detect and fix iptables from running the shell script in the previous section.
- Without looking at the table above, list tips for troubleshooting iptables.
- After completing this lab, how does the above-mentioned shell script work to cause problems with iptables?
