Walls & Guards

Here's an unsettling fact followed fast by a comforting one. The unsettling: machines on the internet get knocked on constantly — automated probes sweep the whole address space around the clock, rattling doors, an ambient weather of opportunistic knocking that never stops. The comforting: you've lived in that weather for years and mostly never noticed. Someone's been working your door this whole time. This lesson introduces the guard.

The firewall

A firewall checks traffic against rules and lets through only what the rules allow. (The name is borrowed from the literal walls in buildings and cars built to stop fire spreading — a barrier by design.) Mapped to the city: the security desk in a building's lobby. Deliveries you asked for come straight up; strangers who arrive unannounced, wanting to "check something," meet the desk.

The heart of a home firewall is one gloriously simple rule: conversations may start from inside, not from outside. Your device asks out — the reply is expected mail, waved through. A stranger's parcel arrives with no conversation to belong to — ignored. Not even refused with a note: dropped in silence, so the prober can't learn whether anyone lives here.

Sound familiar? It should — it's NAT's notebook from Unit 2 wearing a badge. A parcel from outside is deliverable only if the notebook pairs it with a conversation a room started; unsolicited knocks match no line and go nowhere. Your router does run a firewall proper on top, but the deep reason your home rides out the ambient weather is structural: the front desk literally has no idea which room an uninvited parcel could mean. Devices also carry a personal guard of their own — your laptop's built-in firewall — for a layered defense: lobby desk plus a lock on each apartment. (Layered, always layered — the vault-keepers over in Database Foundations I sing the same hymn.)

Safety in shared hallways

The guard covers your building. Step into networks you don't own — café, airport, hotel — and a few habits cover the rest. Not paranoia; the network equivalent of looking before crossing:

• The seal does the heavy lifting. On public Wi-Fi, strangers share your hallway (Unit 1 said it plainly: radio is a room where everyone talks). HTTPS was built for exactly this — padlocked traffic is noise to the neighbor with curious ears. On someone else's network, padlock-only is the rule that matters most.
• Mind the network's own name. A network is whoever runs it. "Free_Airport_WiFi" versus "Free Airport WiFi" — one is the airport's, one is a stranger's laptop three seats away, and joining the wrong hallway hands its owner your traffic patterns. When it matters, ask staff which is real.
• Updates are the walls' maintenance. Those probes hunt one thing: doors with known-broken locks that owners never repaired. Updating your devices and your router's own software is patching the locks — the least glamorous, most effective security act a person can take.

That's the city's security detail: silent desks, sealed envelopes, maintained locks — layers, so no single one has to be perfect.

One lesson remains in this course. Everything works — until the evening it doesn't, and the cry goes up: the Wi-Fi is broken! The finale turns everything you've learned into the calm, layer-by-layer way to find out what's actually wrong — and fix the half of it that's yours to fix.