IP addressing & subnetting · Lesson 6 of 9 · 3 min read
IPv6 essentials
Format
- 128 bits, written as eight groups of four hex digits:
2001:0db8:0000:0000:0000:ff00:0042:8329. - Compression: drop leading zeros in a group (
0db8→db8), and replace one run of all-zero groups with::→2001:db8::ff00:42:8329. - Prefix notation as in IPv4:
2001:db8:abcd::/48. A standard LAN subnet is /64 (64 bits network, 64 bits interface ID).
Enlarge diagram
Swipe sideways to see all of it, or tap to open it full screen.
Address types
| Type | Prefix | Notes |
|---|---|---|
| Global unicast | 2000::/3 |
Publicly routable |
| Link-local | fe80::/10 |
Every interface has one; not routed |
| Unique local (ULA) | fc00::/7 |
Private-like, not routed on the internet |
| Multicast | ff00::/8 |
IPv6 has no broadcast; multicast replaces it |
| Loopback | ::1 |
|
| Unspecified | :: |
Hosts can configure themselves with SLAAC (from router advertisements) or DHCPv6. ARP is replaced by Neighbor Discovery (ICMPv6) — so blocking ICMPv6 breaks IPv6.
IPv6 in AWS and Kubernetes
- VPCs can get an Amazon-provided
/56(or BYOIP); subnets get/64s. Dual-stack or IPv6-only subnets are supported. - IPv6 addresses are globally unique — there's no NAT. For outbound-only internet access use an egress-only internet gateway (stateful, blocks inbound initiation). NAT64/DNS64 lets IPv6-only workloads reach IPv4 services.
- EKS IPv6 clusters give each pod an IPv6 address from the node's prefix — practically unlimited pod IPs, solving IPv4 exhaustion (with some ecosystem caveats).
- With AWS now charging for public IPv4 addresses, IPv6 has a cost angle too.