Tracing the Path

Time to cash in the whole unit. You tap a link on your phone — say, a page on learn.example.com — and somewhere far away a server speaks back within a blink. This capstone follows that one tap the entire way, every stop named with a word you now own. Read it slowly once; after that, you'll never be able to not see it.

The journey out

Stop 0 — the phone orients itself. Long before the tap: when your phone joined the Wi-Fi, the front desk (DHCP) leased it a private room number — 192.168.0.23 — and handed over the key folder: the gateway is the router; here's who to ask about names. Everything below leans on that folder.

Stop 1 — the name becomes a number. learn.example.com is a name, and parcels demand numbers. Phone book first: the DNS lookup hops its right-to-left relay and returns 203.0.113.7. Cached from this morning? The step takes no time at all.

Stop 2 — the request becomes packets. The request is chopped into parcels, each labeled: to 203.0.113.7, door 443 (the web's agreed knock), from 192.168.0.23, door 50871 (a spare one picked for the reply), numbered 1 of n.

Stop 3 — out the front door. Destination not local, so the rule from the key folder fires: hand it to the gateway. The router's front desk (NAT) rewrites the sender line — private room out, the house's one public address in — and jots the notebook line pairing door 50871 with room 23.

Stop 4 — the relay. Now the guild: your provider's neighborhood equipment, its regional sorting centers, a backbone, perhaps an ocean floor, then down into the destination's provider — ten-ish hops, each router reading the label's broad part and passing the parcel closer. Two parcels may ride different roads. Every hop is a sliver of the latency you feel.

Stop 5 — the server's door. The parcels arrive at 203.0.113.7, knock on door 443, where the web server has been listening all along. Reassembly puts the request back in order. The server reads it: one page, please.

The journey back

The reply — the page, chopped into its own numbered parcels — makes the mirror trip: addressed to your house's public address, door 50871. Back through the relay (not necessarily the same roads). At your building, NAT checks the notebook — door 50871, that's room 23 — rewrites the label, and the mail-room clerk delivers the final meters to your phone alone. Reassembly. Rendering. The page is there, whole, and the entire round trip cost a few hundred milliseconds.

That's the whole machine: two units of ideas, cooperating perfectly, billions of times a day, for everyone at once.

Stand back and notice what kind of thing you now know. This wasn't a metaphor tour — it's the actual sequence, the one network engineers sketch on whiteboards (they even have a tool that lists Stop 4's hops one by one; when the labs arrive for this course, it's the first toy you'll get). What remains for Unit 3 is the life on top: the rules the web speaks, the seals on the envelopes, the buildings full of servers — and what to check, layer by layer, on the day the magic doesn't happen. The City awaits.