1,234
edits
Changes
→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).
Follow the instructions for lab 2b on blackboard.
<!--
===Andrew's sections===
::<span style="color:green;font-size:1.5em;">✓</span>List iptables rules for ALL machines.
::<span style="color:green;font-size:1.5em;">✓</span>Prove that you can ping and ssh from your host machines to all of your vms.
::<span style="color:green;font-size:1.5em;">✓</span>Download and run https://ict.senecacollege.ca/~andrew.smith/ops335/labcheck2b.bash
::<span style="color:green;font-size:1.5em;">✓</span>Be able to explain how you debug a connectivity problem caused by iptables.
-->
==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.<br><br>#Without looking at the table above, list tips for troubleshooting iptables.<br><br>
#After completing this lab, how does the above-mentioned shell script work to cause problems with iptables?
