🌐 Network Devices Explained
The Foundation Every Cloud & DevOps Engineer Needs
Series: Networking Fundamentals for Cloud & DevOps — Part 1 of 6
Before VPCs, subnets, route tables, and security groups make sense, you need to understand what’s happening beneath them. This series builds that foundation — starting with the devices that make networks work.
Why Networking Before Cloud?
I hit a wall during my AWS VPC sessions. Route tables, subnets, gateways, NACLs — the concepts existed in isolation. I could follow steps in the console, but I couldn’t reason about why traffic was or wasn’t flowing.
The fix wasn’t more AWS documentation. It was going back to networking fundamentals. Once I understood what a router actually does — how it makes forwarding decisions, what a routing table really is — the AWS route table stopped being a mysterious config screen and became something I could think through.
That’s what this series is. Six posts covering the networking concepts that directly underpin Cloud and DevOps work. No exam prep framing, no CCNA depth. Just what you actually need.
1. What is a Host?
A host is any device that participates in network communication by sending or receiving traffic.
That’s broader than most people assume. Examples: your laptop, your phone, an EC2 instance, a web server, a virtual machine. The word “host” doesn’t imply a server — your laptop is a host just as much as a data center machine is.
2. Client vs Server — Roles, Not Hardware
A client is a host that initiates a request. A server is a host that responds. The critical point: a server is not a special type of computer. It’s just a computer running software that listens and responds.
Your Browser (Client)
│
│ HTTP Request
▼
Web Server (Server)
│
│ HTTP Response
▼
Your Browser (Client)
The same machine can be a client in one communication and a server in another. Your EC2 running a web app is a server to users hitting it — and a client when it queries RDS.
3. IP Address — The Network Identity
An IP address identifies a host at the network layer and allows packets to be routed toward it. Think of it as a postal address for a device.
IPv4 format: 32 bits, written as 4 octets (each 0–255).
136 . 22 . 17 . 98
───── ─── ─── ───
8 bits 8 bits 8 bits 8 bits
Each octet can hold 0–255 (256 values). When your computer sends a request:
Packet contains:
SRC: 72.45.128.15 ← your IP
DST: 136.22.17.98 ← server's IP
The network uses the destination IP to determine where the packet goes. One thing to keep in mind for later: IP alone isn’t the whole story. On a local network, MAC addresses are also involved — we’ll get to that with switches and ARP.
4. Network — Hosts That Can Talk to Each Other
A network is a logical grouping of hosts that can communicate with each other. Networks can be connected to other networks — that’s how the internet works.
Internet
└── Company Network
├── New York Office
│ ├── Sales
│ ├── Engineering
│ └── Marketing
└── London Office
├── Sales
└── Engineering
└── Home Network
├── Home Wi-Fi
└── School Network
A subnet is a smaller network created within a larger network. This becomes critical in Cloud and DevOps — AWS VPCs are divided into subnets, and understanding why requires understanding networks first.
5. Network Devices
These are the devices that move data through networks. Each has a specific job. Understanding the distinction is foundational — it maps directly to how AWS infrastructure works.
Repeater — Signal Regeneration
Signals degrade over distance. A repeater receives a weakened signal, regenerates it, and sends it onward at full strength.
Host A ──────────────> Repeater ──────────────> Host B
weak signal │ refreshed
regenerates signal
signal
What it does not do: A repeater has no understanding of what the data is or where it belongs. No routing decisions, no intelligence — purely signal regeneration.
Hub — Multi-Port Repeater (The Noisy One)
A hub is essentially a multi-port repeater. It receives a signal on one port and repeats it out to all other ports simultaneously.
PC1
│
│
PC2 ────────── HUB ────────── PC3
│
PC4
PC1 sends to PC3:
PC1 → HUB → PC2 ← also receives it ❌
→ PC3 ← intended recipient ✅
→ PC4 ← also receives it ❌
The problem: everyone receives everyone else’s traffic.
Analogy: A person with a loudspeaker in a room. Everyone hears the message, even if it was meant for one person.
Hubs are essentially obsolete. Modern networks use switches. But understanding the hub’s weakness is what makes the switch’s intelligence meaningful.
Bridge — Learning to Be Selective
A bridge connects two network segments and is smarter than a hub — it can learn which MAC addresses exist on each side and only forward traffic that needs to cross.
Network A Network B
───────── ─────────
PC1 PC3
PC2 ──────── Bridge ──────── PC4
If PC1 sends to PC2 → Bridge BLOCKS it (same side)
If PC1 sends to PC3 → Bridge FORWARDS it (needs to cross)
Hub → blindly repeats traffic to everyone
Bridge → learns and selectively forwards
The bridge works using MAC addresses — the hardware address of each network device. Concept becomes important when we reach switches and ARP.
Switch — The Modern Network Workhorse
A switch is essentially a multi-port bridge. Its primary job is to facilitate communication within a network.
Switch
/ |
PC1 PC2 PC3
10.30.55.11
10.30.55.22
10.30.55.33
PC1 wants to reach PC3:
Switch checks its MAC address table
→ Sends frame directly to PC3 only ✅
→ PC2 receives nothing ✅
All three PCs are on the same network. The switch uses its MAC address table to forward frames directly to the right destination — not to everyone. This is the fundamental advantage over a hub.
Modern Ethernet networks overwhelmingly use switches, not hubs.
Router — Moving Data Between Networks
This is the big one. A router connects different networks and forwards packets between them.
Network A Network B
172.16.20.0/24 172.16.30.0/24
PC ── Switch ── Router ── Switch ── PC
│
Internet
Router interfaces:
├── 172.16.20.1 (faces Network A)
└── 172.16.30.254 (faces Network B)
The router has an IP address in each connected network. A host on Network A that wants to reach Network B sends traffic to the router’s interface on Network A. The router forwards it onward.
This is directly how an AWS Internet Gateway works — it’s the router between your VPC and the internet.
Gateway — The Exit Door of a Network
A default gateway is the router a host uses to leave its local network.
Local network = your neighborhood
Gateway = the road leading out
Your PC
IP: 172.16.20.33
Gateway: 172.16.20.1
│
▼
Router (172.16.20.1)
│
▼
Other Network
Same network? → communicate directly, no gateway needed.
Outside your network? → send to the default gateway.
In AWS: when an EC2 instance sends traffic to the internet, it goes to the VPC router at x.x.x.1 of your subnet — which routes it to the Internet Gateway and out.
Routing Table — The Router’s Decision Book
A router needs to know: “Where should I send this packet?”
It stores this in a routing table:
Destination Network Next Hop / Interface
────────────────────────────────────────────
172.16.20.0/24 Interface 1
172.16.30.0/24 Interface 2
0.0.0.0/0 Internet Gateway
When a packet arrives, the router checks the destination IP, finds the best matching route, and forwards accordingly. The 0.0.0.0/0 entry is the default route — catches anything that doesn’t match a more specific entry and sends it out to the internet.
This is exactly what an AWS Route Table is. Not a metaphor — the concepts are identical. When you add a route 0.0.0.0/0 → igw-xxxxx in your VPC, you’re doing the same thing a network engineer does when configuring a router.
Device Summary
| Device | Basic Job | Intelligence |
|---|---|---|
| Repeater | Regenerates signal | None — purely physical |
| Hub | Repeats signal to all ports | None — blindly broadcasts |
| Bridge | Connects segments, filters by MAC | Low — learns MAC addresses |
| Switch | Forwards frames within a network | Medium — MAC address table |
| Router | Routes packets between networks | High — IP routing table |
The memory trick:
- Switch = Same network
- Router = Different networks
How This Maps to AWS
| AWS Component | Networking Equivalent |
|---|---|
| VPC | Your network |
| Subnet | A smaller network within the VPC |
| Internet Gateway | The router connecting VPC to internet |
| Route Table | The routing table on that router |
| Security Group | Firewall at the host level |
| NACL | Firewall at the network boundary |
VPC Router (x.x.x.1) |
Default gateway for all subnets |
Every time you configure a VPC route table, you’re doing what a network engineer does when configuring a router’s routing table. The abstraction changes — the concept doesn’t.
What’s Next
Part 2 covers the OSI Model — not to memorize seven layers, but to understand why each layer exists and what problem it solves. That understanding is what makes protocols like TCP, IP, DNS, and TLS stop being black boxes.
Part 1 of 6 — Networking Fundamentals for Cloud & DevOps
A prerequisite series before diving into AWS VPC, Route Tables, and Network Architecture.
