Start here — 18 lessons, one path
The catalog is a reference library, and a library is a bad place to begin. This path puts 18 protocols in an order where each lesson only uses ideas introduced earlier, so you are never asked to understand BGP before you have seen a router.
It takes roughly 4–6 hours if you read the flow, open the sandbox and take the quiz for each lesson. Marking a lesson learned is stored locally in your browser.
Each lesson animates the exchange step by step, with the decoded packet fields for that step.
DNS and HTTP query real endpoints. Everything else is clearly labelled as a simulation.
Two questions per protocol. Wrong answers explain the underlying fact, not just the letter.
Your position on the path
0 of 18 lessons marked learned. Progress stays in this browser.
1. Bits, frames and addresses
Start at the wire: how bits become frames, how frames find a neighbour, and how IP addresses describe a network.
Every protocol above this one assumes a frame can already move between two network cards.
The same frame problem solved over radio, where you cannot hear while you transmit.
Read first: Ethernet (802.3)
How one physical switch carries several isolated networks without extra hardware.
Read first: Ethernet (802.3)
Why redundant switch links are blocked on purpose, and what happens when they are not.
Read first: Ethernet (802.3), VLAN
The addressing and forwarding model the internet was built on.
Read first: Ethernet (802.3)
How a host turns an IP address into a MAC address on the local segment.
Read first: Ethernet (802.3), IPv4
2. Conversations
Two ways to move data between programs: fire-and-forget datagrams, or an ordered reliable stream.
3. Finding the way
Devices need an address, a name service and a way to report problems before useful traffic can flow.
How a device gets an address before it can talk to anything else.
Read first: Ethernet (802.3), IPv4, UDP
4. The web and its lock
The request/response model that carries the web, and the encryption layer that makes it safe to use.
Methods, status codes, headers and the keep-alive connection model.
How the modern web multiplexes many requests over one connection without head-of-line blocking per request.
Read first: HTTP / HTTPS, TCP
5. Networks at scale
How separate networks agree on routes, how addressing scales past 32 bits, and why clocks matter.
How routers inside one organisation agree on a shortest-path tree.
Read first: IPv4, Ethernet (802.3)
Finished the path?
The coverage map shows the professional tier, the reference registry and the standards still to be written.