Routers and the Journey of a Packet

Lesson 6 · taught by Pip

A packet almost never reaches its destination in one leap. It travels in short hops, handed from one machine to the next, until it arrives. The machines doing that handing are called routers.

Here's the plain idea: a router is a signpost at a crossroads. It doesn't carry your packet the whole way. It just looks at where the packet is headed, points it down the best road, and lets the next signpost take over.

The relay race

Think of mailing a postcard from a small town. Your local post office doesn't drive it across the country. It sends it to a regional hub, which sends it to a bigger hub, which sends it toward the destination's region, then down to their local office, then to the door.

A packet's voyage works the same way. It leaves your home router, hops to your internet provider's router, then to a larger router, then across the backbone of the internet, then down toward the network that holds the address you're after. Each router is one runner in a relay race, and the packet is the baton.

What does each router actually do? It reads the destination IP address on the packet (the number we met in lesson 4), checks its routing table — a kind of "for this destination, send it this way" cheat sheet — and forwards the packet out the best door. That's it. Quick glance, quick handoff, next.

Many paths, no fixed route

Here's the part that surprises people. The packet's route isn't planned in advance. No one drew a line from you to the destination. Each router decides the next hop on its own, in the moment.

That makes the internet wonderfully sturdy. If one road is jammed or a router goes down, the next signpost simply points the packet down a different road. Send ten packets and they might take ten slightly different paths, yet still arrive and get reassembled in order (remember the numbered postcards from lesson 3).

It also explains why distance and congestion matter. More hops, or busier hops, mean a slower trip — which is why a page hosted across the ocean can feel a beat slower than one nearby.

There's a tidy safety rule baked in, too. Each packet carries a small "hop counter" that ticks down at every router. If it ever hits zero — say it got stuck circling — the packet is dropped instead of wandering forever. A lost letter, not an endless one. 🔦

Your turn

On a computer, open a terminal and run traceroute portmint.com (Mac or Linux) or tracert portmint.com (Windows). Each numbered line is one router — one runner in the relay. Count the hops and notice the addresses change as your packet travels outward.

Next we'll look at the rulebook all these machines quietly agree on — that's lesson 7, Protocols.