IPv6 Subnet Calculator Guide

IPv6 Subnet Calculator Guide

IPv6 subnetting uses 128-bit addresses. Unlike IPv4, every link segment is a /64 by default because SLAAC requires that fixed host-portion size to auto-configure interface addresses.¹ Planning an IPv6 address scheme means allocating /48s for sites, /64s for segments, and /128s for specific host routes.

Modern ISPs hand out a /48 to residential and small-business customers, providing 65,536 /64 subnets for one per VLAN or LAN segment.² Dual-stack deployments run IPv4 and IPv6 simultaneously, which means planning two separate CIDR trees that mirror each other. Cloud providers like AWS and Azure also require IPv6 CIDR blocks attached to VPCs, adding a second addressing layer to your infrastructure.

IPv6 prefix mechanics

Inside a /48 allocation, the third 16-bit group identifies the subnet, giving 65,536 distinct /64 subnets for any site-level deployment.³ Each /64 segment contains 2^64 addresses, more than enough for every device conceivable on a single LAN. This abundance means you never need to calculate host counts per subnet the way IPv4 forces you to, because every segment has more addresses than it will ever consume.

SLAAC requirements and /64 boundaries

SLAAC (Stateless Address Autoconfiguration) requires /64 boundaries because it embeds the 64-bit EUI-64 MAC-derived identifier into the host portion.⁴ Consequently, subnets smaller than /64 break SLAAC entirely and are incompatible with the majority of IPv6-capable operating systems. Building on this, /128 addresses a single host, equivalent to IPv4's /32, used in host routes, loopback addresses (::1/128), and security group rules targeting a specific server.

Dual-stack planning

Dual-stack networks run IPv4 and IPv6 simultaneously on every interface, requiring two separate CIDR trees that do not interfere with each other. A practical dual-stack plan mirrors the IPv4 VLAN structure in IPv6: VLAN 10 in IPv4 gets 10.0.10.0/24, and in IPv6 gets a /64 drawn from the site /48 (for example, 2001:db8:1:10::/64). This mirroring approach keeps firewall rules and routing tables intuitive.

Cloud provider dual-stack considerations

AWS VPCs support IPv6 CIDR blocks alongside the primary IPv4 CIDR, with each subnet receiving a /64 from the VPC /56 or /48 block.⁵ Azure VNets assign /48 or /56 prefixes per VNet, then distribute /64 per subnet.⁶ Consequently, the dual-stack plan doubles the number of CIDR ranges to track, making an IPAM or spreadsheet allocation essential before deploying resources.

Reserve IPv6 space for future growth the same way you reserve IPv4. A site that expects only a handful of VLANs today may add IoT, guest, and management segments later, and burning through a /48 too quickly forces a painful renumber. CapyToolkit shows each subnet boundary so you can confirm the IPv6 /64 lines up with the matching IPv4 /24 before you submit the cloud console form.

Using the calculator with IPv6 prefixes

Enter any IPv6 address, formatted with colons and optional :: compression, into the calculator. The tool auto-detects the address family and switches to 128-bit mode. Set the prefix to /48 to see the site allocation boundary, or /64 to see the standard segment. Results include the compressed network address, first host, last host, and total address count. Consequently, you can use the subnet calculator to plan IPv6 /64 subnets for Kubernetes pods, and verify that your /64 subnet boundaries align correctly before committing them to router configs or cloud console forms.

Comparing IPv4 and IPv6 results side by side

For dual-stack work, open two browser tabs, one with your IPv4 CIDR and one with the IPv6 prefix, and compare the output side by side to confirm your VLAN-to-subnet mapping is consistent across both protocols. This catches mismatches where an IPv4 /24 maps to a different VLAN number than the corresponding IPv6 /64, which would cause asymmetric routing in a dual-stack environment.

NDP and IPv6 neighbor discovery on local segments

IPv6 Neighbor Discovery Protocol (NDP) replaces ARP with a more robust mechanism that operates over ICMPv6.⁷ When an IPv6 host needs the MAC address for a destination on the same segment, it sends a Neighbor Solicitation (NS) to the solicited-node multicast address (ff02::1:ffxx:xxxx, derived from the last 24 bits of the target address). Only hosts whose addresses match that suffix respond with a Neighbor Advertisement (NA), reducing unnecessary interruptions compared to ARP's broadcast-everyone approach.

Building on this, NDP also handles router discovery: hosts listen for Router Advertisements (RA) that carry the prefix, default gateway, and flags (M for managed, O for other configuration). The BE900 and other IPv6-capable routers send RAs on each LAN segment. If you run into connectivity issues where devices have link-local addresses but no global IPv6, check that the router's RA is reaching the segment. Wireshark filtering for icmpv6.type==135 (NS) and icmpv6.type==136 (NA) reveals whether neighbor discovery is functioning correctly.⁸

IPv6 subnetting for container and Kubernetes networks

Container runtimes and Kubernetes CNI plugins consume IPv6 address space differently than traditional VMs. With Azure CNI or AWS VPC CNI for EKS, each pod receives a VNet IP from the node's subnet, meaning the node subnet must be large enough for the maximum pod count per node. A /24 node subnet (251 usable in AWS) supports 110 pods per node (the default Kubernetes limit) with headroom for system pods and daemonsets.⁹

For IPv6, the calculation changes: each node receives a /64 from the pod CIDR, and every pod on that node draws from that /64's 2^64 addresses. Building on this, a /56 cluster pod CIDR provides 256 node /64s, enough for a 200-node cluster with room to grow. The subnet calculator's IPv6 mode shows the first and last addresses in each /64, which you can paste directly into your CNI configuration (for example, the aws-node daemonset's WARM_IP_TARGET and MINIMUM_IP_TARGET settings). Consequently, planning IPv6 pod CIDRs with the same rigor as IPv4 prevents the address exhaustion that silently breaks pod scheduling.

When to use this

Use this calculator when planning a new IPv6 address scheme, verifying dual-stack configurations, or checking that your ISP /48 allocation provides enough /64 subnets for your VLAN count.

Examples