Network hardware forms the physical foundation of any network. Understanding these components helps you design, troubleshoot, and optimize your infrastructure.
Network Devices Overview
User Devices ← → Switch ← → Router ← → Internet
(Computers) (Layer 2) (Layer 3)
Core Network Devices
1. Network Interface Card (NIC)
The hardware that connects a device to a network.
Physical NIC:
- Installed in servers, computers, network appliances
- Has a unique MAC address burned into it
- Connects to network via Ethernet cable or WiFi
Virtual NIC:
- Software-based in containers, VMs, and cloud instances
- Still has a MAC address, but it's software-assigned
- Functions identically to physical NICs
Example: A server might have 2 physical NICs for redundancy; a container might have 1 virtual NIC.
2. Switch (Layer 2 Device)
Connects devices within a local network (LAN).
How it works:
- Learns MAC addresses of connected devices
- Forwards frames based on destination MAC address
- Creates dedicated connections between ports
- Operates at Layer 2 (Data Link Layer)
Key features:
- Managed Switch: Can be configured, monitored; supports VLANs
- Unmanaged Switch: Plug-and-play; no configuration
In DevOps:
- Physical switches in data centers
- Virtual switches in hypervisors (vSwitch) and container platforms
3. Router (Layer 3 Device)
Connects different networks together; forwards packets between them.
How it works:
- Looks at IP addresses (Layer 3)
- Maintains routing tables showing how to reach destinations
- Forwards packets based on destination IP
- Acts as a gateway between networks
Key concepts:
- Gateway — the router's IP address on a network (where devices send non-local traffic)
- Routing table — map of destinations and which interface/next-hop to use
- Default gateway — where packets go if no specific route matches
Example:
192.168.1.0/24 network 10.0.0.0/8 network
(Home office) (Remote office)
↓ ↓
Router A ← → Internet ← → Router B
(GW: 192.168.1.1) (GW: 10.0.0.1)
4. Gateway
A device or service that provides access between networks.
Types:
- Network Gateway — router connecting to the internet
- API Gateway — connects clients to backend services
- VPN Gateway — provides secure connections to remote networks
- Application Gateway — application-level gateway (Layer 7)
In DevOps context:
- Cloud providers (AWS, Azure, GCP) provide managed gateways
- Kubernetes ingresses act as gateways to cluster services
5. Firewall
Security device that controls traffic between networks.
Hardware Firewall:
- Physical device positioned between internal network and internet
- Protects entire network
Software Firewall:
- Runs on individual devices (iptables, Windows Defender)
- Protects that specific device
Stateful Firewall:
- Tracks active connections
- Allows return traffic automatically
- "Smarter" than simple packet filtering
In DevOps:
- Firewalls at network perimeter
- Software firewalls in containers/VMs
- Network policies in Kubernetes
Network Media and Connections
Wired Connections
Ethernet:
- Most common wired technology
- Cat 5e, Cat 6, Cat 6a, Cat 7 cables
- Higher categories = faster speeds, better shielding
| Category | Speed | Distance |
|---|---|---|
| Cat 5e | 1 Gbps | 100m |
| Cat 6 | 10 Gbps | 55m |
| Cat 6a | 10 Gbps | 100m |
| Cat 7 | 10 Gbps | 100m |
Fiber Optic:
- Higher speeds (up to 400 Gbps commercially)
- Longer distances without signal degradation
- More expensive than copper
- Used for backbone connections
Wireless Connections
WiFi (802.11):
- Most common wireless technology
- Different standards: 802.11a/b/g/n/ac/ax (WiFi 6)
- WiFi 6 (802.11ax) — latest, faster, lower latency
Cellular:
- 4G/LTE, 5G
- Used for mobile devices and IoT
Network Interfaces Configuration
IP Address Assignment
Manual (Static):
IP: 192.168.1.100
Netmask: 255.255.255.0
Gateway: 192.168.1.1
DNS: 8.8.8.8
Automatic (Dynamic - DHCP):
- Device gets an IP lease from a DHCP server
- Lease expires and must be renewed
- Used in most home and office networks
Link-Local (169.254.x.x):
- Assigned automatically if DHCP fails
- Used for temporary troubleshooting
Multi-Homing and Bonding
Multi-Homed Device
A device with multiple network interfaces:
- Each NIC can connect to different networks
- Each NIC has its own IP address
- Common in servers, routers, firewalls
Example:
Server:
- eth0: 192.168.1.50 (company LAN)
- eth1: 10.0.0.50 (storage network)
- eth2: 203.0.113.50 (public internet)
NIC Bonding / Teaming
Combining multiple NICs for redundancy or higher throughput:
- Active-Active: Both NICs carry traffic (higher throughput)
- Active-Passive: One active, one backup (high availability)
- Load Balance: Traffic split across multiple NICs
In DevOps:
- Server redundancy for critical systems
- Database clusters often use bonded NICs
DevOps Hardware Best Practices
| Practice | Benefit |
|---|---|
| Multi-homed setup | Redundancy, separation of concerns |
| Bonded NICs | High availability and throughput |
| Managed switches | VLANs, monitoring, control |
| Redundant gateways | No single point of failure |
| Proper cabling (Cat 6+) | Future-proof for higher speeds |
| Regular firmware updates | Security and stability |
Summary
Understanding network hardware:
- NICs connect devices to networks
- Switches connect devices locally (Layer 2)
- Routers connect networks together (Layer 3)
- Gateways provide access between network types
- Firewalls control traffic for security
- Wired (Ethernet, Fiber) and wireless connections serve different needs
- Multi-homing and bonding provide redundancy and performance