Subnetting Cheat Sheet: CIDR Mental Math, AWS Reserved IPs and an Interactive Speed Game

"You are provisioning a new VPC with 10.0.0.0/22. Carve out subnets for Web, Application, and Database tiers across 3 Availability Zones without overlapping CIDRs. What are the subnet masks, broadcast addresses, and total usable IP ranges per tier?"

The High-Density Pod Trap

Unlike overlay networks (Flannel/VXLAN) that encapsulate packets in tunnels, the AWS VPC CNI assigns real private IPv4 addresses from the node's underlying VPC subnet directly to every Pod.

• An m5.2xlarge instance can host up to 58 pods across multiple ENIs.
• A conservatively sized /26 subnet has only 59 usable IPs in AWS.
• Two worker nodes will consume 100% of the available IP pool.

When the cluster autoscaler tries to spin up a third node, pods fail with:

failed to assign an IP address to container: no free IP addresses available in subnet

Pods remain stuck in ContainerCreating or CrashLoopBackOff. Autoscaling completely halts.

Magic Number = 256 − Interesting Octet Mask

The "Interesting Octet" is the specific octet where the subnet mask changes from 255 to something other than 0.

Step 1 — Find the Interesting Octet & Mask:
A /24 uses octets 1-3 → 255.255.255.0.
A /27 adds 3 more bits into the 4th octet: 128 + 64 + 32 = 224.
Full mask: 255.255.255.224.

Step 2 — Apply Magic Number:
256 − 224 = 32

Step 3 — Step through subnet boundaries (increments of 32):

Step 4 — Pinpoint 192.168.1.75:
Falls between .64 and .95 → Subnet 2.

• Network Address: 192.168.1.64
• First Usable Host: 192.168.1.65
• Last Usable Host: 192.168.1.94
• Broadcast Address: 192.168.1.95
• RFC Usable Hosts: 32 − 2 = 30

How Prefix Delegation Solves IP Exhaustion

Instead of assigning individual /32 IPs to each pod, the VPC CNI assigns a /28 IPv4 prefix (16 addresses) to each ENI on your EC2 node.

Enable Prefix Delegation (One Command)

# Step 1: Enable prefix delegation on the aws-node DaemonSet
kubectl set env daemonset aws-node \
  -n kube-system \
  ENABLE_PREFIX_DELEGATION=true

# Step 2: Set warm prefix target (optional, reduces startup latency)
kubectl set env daemonset aws-node \
  -n kube-system \
  WARM_PREFIX_TARGET=1

# Step 3: Verify — nodes should now show higher pod capacity
kubectl get nodes -o custom-columns=\
'NAME:.metadata.name,CAPACITY:.status.capacity.pods'

⚠️ Requires: VPC CNI v1.9+, EKS 1.21+, and instance types that support multiple ENIs. Nitro-based instances (m5, c5, r5 families) are fully supported.

What AWS IPAM Does

• Centralized CIDR tracking — Single pane of glass across all VPCs, accounts, and regions.
• Automated allocation — Assigns CIDR blocks to new VPCs from a pre-defined pool, preventing overlaps.
• Compliance auditing — Flags unallocated, over-utilized, or overlapping CIDRs.
• Transit Gateway safety — Ensures spoke VPCs never receive overlapping CIDRs that would break TGW routing.

When You Need IPAM

# Terraform: Create an IPAM pool for production VPCs
resource "aws_vpc_ipam" "main" {
  operating_regions {
    region_name = "us-east-1"
  }
}

resource "aws_vpc_ipam_pool" "prod" {
  address_family = "ipv4"
  ipam_scope_id  = aws_vpc_ipam.main.private_default_scope_id
  locale         = "us-east-1"
}

resource "aws_vpc_ipam_pool_cidr" "prod_cidr" {
  ipam_pool_id = aws_vpc_ipam_pool.prod.id
  cidr         = "10.0.0.0/8"  # Master pool — all VPCs carved from here
}

# VPC auto-gets a /24 from the IPAM pool — no manual CIDR selection needed
resource "aws_vpc" "app" {
  ipv4_ipam_pool_id   = aws_vpc_ipam_pool.prod.id
  ipv4_netmask_length = 24
}

CCNA & Network+ Subnetting Exam Tips

Subnetting questions appear in every CCNA (200-301) and Network+ (N10-009) exam. The question formats you'll encounter:

• Given an IP and prefix, find the network address, broadcast, first/last usable host
• Given a requirement (e.g., "need 50 hosts"), find the minimum CIDR prefix
• Given an address range, determine if two IPs are in the same subnet
• Calculate the number of subnets created by borrowing N bits

The Magic Number method solves all four types in under 5 seconds. Practice with the CIDR Speed Challenge until it's automatic.

CKA Exam Networking (Kubernetes Certified Administrator)

For the CKA exam, subnetting knowledge is tested through:

• Configuring --pod-network-cidr and --service-cidr during kubeadm init
• Understanding why Pod CIDRs must not overlap with node or service CIDRs
• Troubleshooting CNI connectivity failures caused by exhausted or overlapping CIDR ranges

# CKA Exam: Initialize cluster with non-overlapping CIDRs
kubeadm init \
  --pod-network-cidr=192.168.0.0/16 \
  --service-cidr=10.96.0.0/12

# Verify pod and service CIDRs don't overlap with your node subnet
kubectl cluster-info dump | grep -E "podCIDR|serviceCluster"

IPv6: The Long-Term Solution to IP Exhaustion

IPv6 adoption in AWS VPC is the #1 trending topic for cloud architects in 2025. With a /56 block per VPC providing 4.7 × 10²⁴ addresses, IP exhaustion becomes mathematically impossible.

# Enable IPv6 on existing VPC and subnets (Terraform)
resource "aws_vpc" "main" {
  cidr_block                       = "10.0.0.0/16"
  assign_generated_ipv6_cidr_block = true  # AWS assigns a /56
}

resource "aws_subnet" "app" {
  vpc_id                          = aws_vpc.main.id
  cidr_block                      = "10.0.1.0/24"
  ipv6_cidr_block                 = cidrsubnet(aws_vpc.main.ipv6_cidr_block, 8, 1)
  assign_ipv6_address_on_creation = true
}

Great platform engineers don't rely on crutches for foundational networking math. Master the Magic Number, account for cloud provider reservations, and drill your reflexes until CIDR calculations become second nature.