IP addressing & subnetting · Lesson 3 of 9 · 3 min read
Private, special and reserved ranges
RFC 1918 private ranges
| Range | CIDR | Size | Lives in old class space |
|---|---|---|---|
| 10.0.0.0 – 10.255.255.255 | 10.0.0.0/8 | 16.7 million | A |
| 172.16.0.0 – 172.31.255.255 | 172.16.0.0/12 | 1 million | B (16 Class Bs) |
| 192.168.0.0 – 192.168.255.255 | 192.168.0.0/16 | 65,536 | C (256 Class Cs) |
Private addresses are not routed on the internet. Anyone can use them internally; to reach the internet they need NAT. Note the trap: 172.32.0.1 is public — the private block ends at 172.31.
Enlarge diagram
Swipe sideways to see all of it, or tap to open it full screen.
Other special ranges
| Range | Meaning |
|---|---|
127.0.0.0/8 |
Loopback |
0.0.0.0/8 |
"This network"; 0.0.0.0 = unspecified / all interfaces when binding |
169.254.0.0/16 |
Link-local (APIPA — self-assigned when DHCP fails). AWS uses it for the instance metadata service 169.254.169.254, the time service 169.254.169.123, and the DNS resolver alias 169.254.169.253 |
100.64.0.0/10 |
Carrier-grade NAT shared space (RFC 6598); commonly used for EKS secondary CIDRs for pod IPs because it rarely clashes with corporate ranges |
224.0.0.0/4 |
Multicast (Class D) |
240.0.0.0/4 |
Reserved (Class E) |
255.255.255.255 |
Limited broadcast |
192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24 |
Documentation examples (TEST-NET) |
198.18.0.0/15 |
Benchmarking |
Public vs private
- Public IPs are globally unique and routable on the internet (assigned via RIRs — APNIC for India — and ISPs/cloud providers).
- Private IPs are reusable internally; internet access needs NAT, and the internet can't initiate connections to them — NAT only allows outbound-initiated flows (or explicit port forwarding).
- In AWS, an instance has a private IP on its ENI; a public IP or Elastic IP is mapped to it 1:1 by the internet gateway — the instance's OS never sees the public address.
Enlarge diagram
Swipe sideways to see all of it, or tap to open it full screen.