Labs / Troubleshooting

TroubleshootingThe medal for finishing it

Road 11 of 33

Troubleshooting

Finding out what is broken, and where.

2 groups · 5 labs · builds on Network Basics , Protocols

Start this road

Where it breaks

A method, then a test for each place a fault hides.

  1. 01 Network troubleshooting: find the broken layer, one test at a time Work a real fault like a pro: reproduce, guess, test, fix, check, write.
  2. 02 Ping and traceroute: find where a path goes slow, lossy or round in circles Read ping and traceroute like a pro to find where lag and loss start.
  3. 03 Is it DNS? Find where a name lookup breaks, and prove when it doesn't DNS troubleshooting: find which part of a lookup failed, or prove it isn't DNS.
  4. 04 What's listening? Tell a refused port from a blocked one, and find who holds it Check open ports, Linux side and network side: closed or blocked, and who holds each.

Reading the counters

Finding a bad port or cable from what it says.

  1. 01 Cable and interface errors: read a port's state and counters, and find the bad link Read port states and counters to find a switched-off port, bad cable or MTU clash.

What its labs use

Concepts

Commands

Learn it on real machines.

Every lab is a small network of real Linux machines in your browser. Sign in with Google or email to start.

Start this lab