Network Devices Explained — The Foundation Every Cloud & DevOps Engineer Needs

🌐 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 at the physical and logical level 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 a broader definition 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. Your phone is a host. In AWS terms, every EC2 instance is a host — it sends and receives traffic just like any other device on a network. 2. Client vs Server — The Roles, Not the Hardware This distinction matters more than it seems. A client is a host that initiates a request. A server is a host that responds to that request. The critical point: a server is not a special type of computer. It's just a computer running software that listens for and responds to requests. The same machine can be a client in one communication and a server in another. Your browser (client) → sends HTTP Request → Web Server (server) → sends HTTP Response → Your browser Your browser is the client when requesting a webpage. That web server is a client when it queries a database. Same machines, different roles depending on who's initiating. In AWS, your EC2 instance running a web application is a server to the users hitting it — and a client to the RDS database it queries. 3. IP Address — The Network Identity An IP address identifies a host at the network layer and allows packets to be addressed and routed toward that host. Think of it as a postal address for a device. Without one, there's no way to specify where a packet should go. IPv4 format: 32 bits, written as 4 octets (groups of 8 bits), each 0–255. 136.22.17.98 breaks down as: 136 22 17 98 8 bits 8 bits 8 bits 8 bits Each octet: 0–255 (256 possible values) When your computer sends a request to a web server, the 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 needs to go. 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 when we reach 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. A useful mental model: 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 very important in Cloud and DevOps work — AWS VPCs are divided into subnets, and understanding why requires understanding networks first. 5. Network Devices — What Each One Does Now the main section. These are the physical (and virtual) devices that move data through networks. Each one has a specific job. Understanding the distinction between them 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 weak signal Repeater refreshed signal Host B ↓ What it does not do: A repeater has no understanding of what the data is or where it belongs. It just amplifies and re-sends. 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. The problem: everyone receives everyone else's traffic. HUB PC1 PC2 PC3 PC4 PC1 sends to PC3: PC2 and PC4 also receive it 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 because it can learn which MAC addresses exist on each side. Network A PC1, PC2 Bridge Network B PC3, PC4 Knows which hosts are on which side Only forwards traffic that needs to cross If PC1 sends to PC2 (both on Network A), the bridge blocks it from crossing to Network B. If PC1 sends to PC3 (Network B), the bridge forwards it across. Hub → blindly repeats traffic to everyone Bridge → learns and selectively forwards The bridge works using MAC addresses — the hardware address of each network device. This concept becomes important when we study 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 10.30.55.11 PC2 10.30.55.22 PC3 10.30.55.33 PC1 → PC3: only PC3 receives it ✅ All three PCs are on the same network (10.30.55.x). If PC1 wants to communicate with PC3, the switch uses its MAC address table to forward the frame directly to PC3 — not to PC2, not to everyone. This is the fundamental advantage over a hub. The switch is intelligent about delivery. 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 172.16.20.0/24 Switch Router 172.16.20.1 172.16.30.254 Switch Network B 172.16.30.0/24 Internet The router has an IP address in each connected network — acting as the bridge between them. A host on Network A that wants to reach Network B sends its traffic to the router's IP address on Network A. The router forwards it to Network B. This is directly how an AWS Internet Gateway works — it's the router between your VPC (private network) and the internet (another network). 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 of your neighborhood If a host wants to communicate with another host inside its own network, it doesn't need the gateway. If it wants to reach something outside its network, it sends traffic to the default gateway — which then figures out how to route it further. Your PC IP: 172.16.20.33 GW: 172.16.20.1 Router 172.16.20.1 172.16.30.254 Other Network Same network? → Send directly Different network? → Send to gateway In AWS: when an EC2 instance in your VPC sends traffic to the internet, it goes to the default gateway — the VPC router at x.x.x.1 of your subnet's CIDR block — which then 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 to reach that network?" It stores this information in a routing table — a list of destination networks and where to forward traffic to reach them. Router 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. That last entry — 0.0.0.0/0 — is the default route. It catches anything that doesn't match a more specific entry and sends it to the internet gateway. This is exactly what an AWS Route Table is. Not a metaphor — the AWS route table is a routing table. The concepts are identical. The Device Summary Device Basic Job Intelligence Level 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 Not an absolute rule for every modern device — Layer 3 switches exist — but it's the correct foundational model. How This Maps to AWS AWS Component Networking Equivalent VPC Your network Subnet A smaller network within the VPC Internet Gateway The router connecting your VPC to the internet Route Table The routing table on that router Security Group Firewall rules at the host level NACL Firewall rules 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 exactly what a network engineer does when configuring a router's routing table. The abstraction layer 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.