—IPv6 & NAT Planning Calculator
Plan IPv6 hierarchy and canonical addresses, NAT44 port capacity, deterministic CGNAT blocks and logging, plus NAT64/DNS64 synthesis.
IPv6 Prefix Planner · Inputs
Supports compression/expansion, parent-child prefixes, adjacent subnets and up to 32 preview rows.
IPv6 Prefix Planner · Planning results
——————| Index | Subnet CIDR |
|---|
NAT44 Capacity · Inputs
TCP and UDP port spaces are calculated separately; implementation, ALG, timeout and mapping behavior remain vendor-specific.
NAT44 Capacity · Planning results
CGNAT Planner · Inputs
100.64.0.0/10 is the shared address-space reference for provider CGN; confirm port blocks, oversubscription and logging against equipment and regulatory requirements.
CGNAT Planner · Planning results
NAT64 / DNS64 · Inputs
RFC 6052 supports /32, /40, /48, /56, /64 and /96. DNS64 synthesis uses the same IPv4-embedded address format as the NAT64 destination.
Reverse IPv4 extraction
NAT64 / DNS64 · Planning results
———- IPv6 arithmetic uses 128-bit BigInt rather than JavaScript Number.
- Port utilization, session demand and logging values are editable engineering assumptions.
Methodology and standards boundary
METHODOLOGY
IPv6 prefix arithmetic
IPv6 addresses are processed as 128-bit integers. Host bits are cleared by the prefix mask; child-prefix count is 2^(new prefix − parent prefix).
NAT44 capacity
Mapping capacity is estimated from the allocatable port range, reserve, pool utilization and enabled protocol namespaces, then compared with subscriber peak demand including margin.
Deterministic CGNAT
Deterministic subscriber capacity per public IPv4 equals usable ports divided by block size; TCP and UDP normally use the same numeric block independently.
NAT64/DNS64
RFC 6052 embeds IPv4 bits after the selected prefix and reserves the u octet at bits 64–71 when the prefix is shorter than /96.
Frequently asked questions
FAQ
Why are IPv6 subnet address counts so large?
IPv6 has 128 bits. A /64 leaves 64 interface-identifier bits, so it contains 2^64 addresses. The tool shows both exponent and exact integer.
Why is the port range editable?
Platforms may reserve management ports, static mappings or use different pool policies, so 1024–65535 is only a common engineering starting point.
Can TCP and UDP capacity be added?
Their port namespaces are independent and can be estimated separately, but real capacity is also limited by session tables, memory, CPU, timeouts and applications.
Is a smaller deterministic block always better?
Smaller blocks improve public-IPv4 sharing but increase port-exhaustion and application risks; choose them from busy-hour session distributions.
Can the NAT64 well-known prefix represent private IPv4?
RFC 6052 restricts the well-known prefix from representing non-global IPv4. Domain-local deployments can assess a network-specific prefix or the RFC 8215 local-use prefix.
Planning history
PROJECT RECORDS
ENGINEERING WORKFLOW
Continue the engineering workflow
Plan addressing, VLAN capacity, packet size, uplinks, optics, access policy and DNS behavior as one LAN design sequence.