Getting an Address

Think about what you did to connect your phone at a friend's place: asked for the Wi-Fi password, typed it, done. At no point did you type an IP address. Yet last lesson swears your phone holds one there. So somebody assigned it — instantly, invisibly, without either of you being consulted. Time to meet the receptionist.

DHCP: the front-desk protocol

The assigner is a service called DHCP (Dynamic Host Configuration Protocol — a name only a committee could love; "the address desk" serves fine), and in your home it runs inside — where else — the router. The moment a device joins the network, a tiny four-step conversation plays out, faster than you can blink:

• The newcomer, addressless, broadcasts: "Anyone — I'm new. May I have an address?"
• The desk answers: "Welcome. How about 192.168.0.23?"
• "I'll take it."
• "Noted. It's yours — details attached."

Picture a hotel front desk at check-in. You don't wander the halls picking a room you like; the desk assigns one that's free, notes it in the ledger, and hands you a key folder — which, crucially, contains more than the room number. The DHCP answer also tells the newcomer the two facts every device in Unit 1 mysteriously "knew": the way out is that box (the gateway's address) and here's who to ask about names (a bookmark for two lessons from now). One desk visit, fully oriented.

This is why networks feel like magic to join: the entire orientation is automated. It's also why two devices never collide on one address — the desk keeps the ledger, and handing the same room to two guests is the one sin it's built never to commit.

Leases: borrowed, not owned

The desk doesn't give addresses; it leases them. Your phone's address comes with a time limit — commonly a day or so — after which the phone must renew, a quick "still here, keep my room?" that succeeds silently while you notice nothing.

Why bother? Because guests leave without checking out. Phones wander off mid-afternoon; laptops sleep for a week. Without expiry, the ledger fills with rooms held by ghosts, and — with IPv4's scarcity fresh in mind — a network can genuinely run dry. Leases mean an abandoned address quietly returns to the pool for the next arrival. Elegant bookkeeping, zero human effort.

And here's the payoff for your troubleshooting toolkit — the second half of the restart-ritual story lesson 6 promised. When a device insists "connected, no internet," a stale or confused lease is a classic culprit: the device is holding a room key the desk no longer honors. Toggling Wi-Fi off and on forces a fresh check-in — new conversation, clean lease, oriented anew. Restarting the router resets the desk itself, wiping the whole ledger for a fresh start. Neither is superstition; both are check-in do-overs.

So: every device walks in addressless and leaves the front desk with an address, a lease, and directions to the door. But look at the address in that example — 192.168.0.23. You may have seen those first numbers before, on completely different networks. Your home, your school, and a million strangers' routers all deal addresses starting 192.168. Duplicates?! Scandal?! Next lesson: the two-tier address system that makes this not only legal but the trick keeping IPv4 alive.