Learn

Learn networking from real packets.

Step-by-step walkthroughs of short captures, and plain-language guides to every field you'll see. Free, no account needed.

Learning paths

Not sure where to start? Follow a path: walkthroughs, field guides, and challenges in order. All paths

  1. Beginner

    Your first packets

    What happens when you open a web page: names, connections, and requests, one packet at a time.

    8 steps
  2. Beginner

    Privacy and the secure web

    What encryption hides, what it doesn't, and how to tell when it fails.

    6 steps
  3. Beginner

    How your home network works

    How a device joins the network, finds its neighbours, and reaches the internet.

    6 steps
  4. Intermediate

    Troubleshooting like a network engineer

    Find out why something is slow or broken, and prove whether it's the network.

    9 steps
  5. Intermediate

    Voice calls on the network

    How a call is set up, how the audio travels, and what makes it sound bad.

    5 steps

Answers to network problems

Is it the network, DNS, or the server? Short, direct answers for the problems captures show most, with Wireshark filters. Start with the checklist

All 17 answers

Walkthroughs

Each one follows a short capture, one packet at a time. Read it here or open it interactively.

  1. Start here

    Loading a web page

    DNS, TCP, and HTTP working together to fetch one page.

    9 steps, 14 packets Read Interactive
  2. Beginner

    HTTP compared with HTTPS

    The same kind of request, readable over HTTP and encrypted over HTTPS.

    6 steps, 25 packets Read Interactive
  3. Beginner

    Following a DNS lookup

    A name that resolves, a typo that doesn't, and a cached answer.

    5 steps, 6 packets Read Interactive
  4. Beginner

    Joining a network

    How a device gets an address with DHCP, then makes its first connection.

    7 steps, 23 packets Read Interactive
  5. Beginner

    A refused connection

    A reachable device that has nothing listening on the requested port.

    6 steps, 12 packets Read Interactive
  6. Intermediate

    A failed TLS handshake

    A server that can't agree on a TLS version with a modern client.

    4 steps, 11 packets Read Interactive
  7. Intermediate

    Tracing the route

    How traceroute finds every router between you and a server.

    7 steps, 11 packets Read Interactive
  8. Intermediate

    A phone call over the internet

    SIP sets up a call, RTP carries the voice, and a few lost packets cost quality.

    7 steps, 601 packets Read Interactive
  9. Intermediate

    Home office: checkout failing

    A busy home network where one site keeps failing.

    4 steps, 2,268 packets Read Interactive

Test yourself: packet challenges

Short "find the problem" puzzles, from your first DNS error to a lost packet. A new daily challenge every day.

Protocol field guides

What every field in a packet means and why it matters. The same explanations appear in Learn mode inside an analysis.

How the health grade works

Every analysis gets a grade from A to F. It comes from fixed rules, not opinion, so the same capture always gets the same grade.

  1. Four categories. DNS, Connections, Encryption, and Apps & calls. Each finding counts toward one of them. Notes about the capture itself, like seeing only one direction, don't count.
  2. Each starts at 100. The biggest problem takes off its full weight (critical 60, high 40, warning 20, low 8, note 2); every further one takes off half.
  3. Plain HTTP costs points. Encryption loses up to 30 points for the share of web connections that weren't encrypted.
  4. Missing traffic isn't judged. A category with nothing to look at shows a dash instead of a grade.
  5. The weakest spot matters most. The overall score is half the worst category plus half the average, so one serious problem can't hide behind three healthy ones. A is 90 and up, B 80, C 70, D 60, and anything lower is F.

Try it on your own traffic

Record a capture on your computer, then upload it to see the same explanations for your network.