// Foundations

Explore Networking Basics

The internet is just one very large network. Yours doesn't need it to count.

Networking gets taught as a stack of labels — seven layers, a handful of acronyms, memorize and move on. That approach produces students who can recite "Application, Presentation, Session..." and still can't tell you why a switch and a router aren't the same box, or why the home gadget with four ports is quietly doing three different jobs at once.

Here the layers get anchored to things you can point at: a switch forwarding by MAC address, a router making decisions by IP, DNS turning a name you typed into an address a packet can actually use. Nugget draws the path first — the resolver chain, the handshake, the frame-to-packet-to-segment stack — then asks you to work across it, the way you'd actually trace a problem: check the interface, ping the gateway, ping something further out, see where the answers stop.

The habits this builds are diagnostic ones. Once you've traced a DNS lookup by hand or watched a SYN handshake stall, "the internet is down" stops being your first guess and becomes your last resort.

// What a session feels like

You bring the questions. Nugget asks the next one.

  • Nugget sketches the DNS resolution chain — stub resolver, recursive resolver, root, TLD, authoritative — and asks you which step you'd blame if a domain resolves fine on your phone's data but not on the office Wi-Fi.
  • In the terminal, you run ping against the gateway, then an external IP, then nslookup against the same domain — Nugget has you narrow down at which point the failure actually sits before it lets you name a cause.
  • On the whiteboard, Nugget lays out a three-way handshake next to a flood of unanswered SYNs and has you explain why the second one can stall a server without ever completing a connection.

Start exploring Networking Basics tonight — a 30-day trial, cancel anytime.

Start your 30-day trial