Open main menu

CDOT Wiki β


OPS335 Lab 2b

2 bytes removed, 4 January
<table border="1" cellspacing="0" cellpadding="5" >
<tr> <th>1</th><td>'''Test Network Connectivity'''</td><td>You can use the [http steps in lab 1] as a guide, but keep in mind the firewall may be blocking pings and DNS requests.</td></tr>
<tr> <th>2</th><td>'''Verify Service is Running &amp; listening on the correct interfaces'''</td><td>You should learn to read the output of '''ss -atnp''' and '''ss -aunp''' to complement the '''systemctl status''' command.</td></tr>
<tr> <th>3</th><td>'''List your iptables Rules &amp; Perform a "Walk-Thru"'''</td><td>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.<br><br>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?<br><br>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).</td></tr>