Understanding Computer Networks by Analogy | Guillermo Garcia

Skip to content

Pre-Publish Edition<br>Understanding Computer Networks by Analogy

A quiet, literary map of the digital city. Written for the student, the engineer, or anyone who has ever stared at a network timeout and felt personally judged by it.

Buy the Book<br>Look Inside<br>Read the Story

The Mental Model I Didn't Have

From the Introduction

A few years ago, I asked my manager for the chance to go do my first OpenStack deployment at a customer site in Portugal. I went there to install a full on-premises cloud infrastructure. Something I had already done in the lab and at home multiple times.

The lab version made sense. The customer site did not care.

I started to feel the classic cascade issues, where one node would not boot over IPMI. Another server was slow even with 10G links. Package installs failed because the repository was behind a firewall that had not been enabled. DNS was not set up, so the dashboard would not load by name. Virtual machines on different compute nodes could not reach each other because the networking configuration in OpenStack was wrong.

I had worked in labs before where I knew almost every variable. This was different. The cabling mattered. The firewall mattered. DNS mattered. I knew the pieces, but not how they fit together.

A day later, my manager sent the cavalry. Two days later, we were drinking vinho verde.

What stood out was not that he knew more commands. It was how he worked through the problems. He started with basic questions and used simple pictures to guide what to check. He'd say something like this:

"The door isn't stuck on our side. Something is blocking it from the other side, so let's go check there."

Those pictures let him move from one test to the next without getting lost. I could follow the steps, but I did not have the same picture in my head.

That job stayed with me. It showed the gap between knowing the terms and being able to see the layout. This book is my attempt to build that layout for you, room by room, street by street.

The Metaphor Blueprint

The internet is like a city of buildings. Click or hover on a block to reveal the networking logic behind the physical blueprint.

The Analogy<br>A Building

A self-contained structure with multiple floors, doors, and private hallways.

Technical Term<br>Local Area Network (LAN)

A local network segment. Devices inside can talk directly, but leaving requires visiting the lobby gateway.

The Analogy<br>A Room

A specific destination inside the building where work gets done or envelopes are kept.

Technical Term<br>Device / Host

Your laptop, your phone, or a printer. A printer acts like a room that enjoys ruining your afternoon.

The Analogy<br>A Door

The physical boundary of the room. You can have a Wi-Fi door, an Ethernet door, or a software door.

Technical Term<br>Network Interface (NIC)

The entry/exit point of data. A host can have multiple interfaces, each with its own physical path.

The Analogy<br>Door Label

A permanent, physical label printed directly onto the metal plate of the door frame.

Technical Term<br>MAC Address

A unique physical hardware address. Tells the local building switch exactly which door is which.

The Analogy<br>Room Number

A logical room number assigned by the building administration. It changes if you move rooms.

Technical Term<br>IP Address

A logical network address. It places you in the network layout and dictates how the city routes envelopes to you.

The Analogy<br>A Floor

A vertical segment of rooms. Getting to another room on your floor is easy; changing floors takes an elevator.

Technical Term<br>Subnet

An IP range grouping. Devices on the same subnet communicate locally without going through the router.

The Analogy<br>An Envelope

A paper packet containing a return address, a destination address, and a message slipped inside.

Technical Term<br>Network Packet

The basic unit of data. Formatted with headers (addresses) and payload (the actual data bytes).

The Analogy<br>Elevator Lobby

The central lobby floor exit. If an envelope's room number isn't on your floor, you drop it here.

Technical Term<br>Default Gateway

The routing exit node. If a destination address is external, the OS drops the packet at this IP to exit.

The Analogy<br>The Concierge

The lobby concierge with a city map. They know the next street to take, even if they don't know the target room.

Technical Term<br>A Router

A device that examines IP destinations and makes routing decisions, forwarding packets hop-by-hop through the city.

Where the analogy breaks: A router isn't a friendly human concierge making wise choices. It doesn't read your whole letter. It's an optimized packet-switching machine executing simple lookup tables. It does exactly what it's told—even if the instructions are completely wrong.

Inside the Blueprint

We go deep. Over 17 chapters of technical fundamentals translated into tactile, visual maps. Expand each part to explore what's inside.

Part...