How this calculation works
Normalize parent host bits, order requests from largest address block to smallest and allocate aligned children consecutively. Keep all address counts as exact integers rather than floating-point approximations.
Block addresses = 2^(128 − prefix); align each child to its block size inside the normalized parentA worked example
Inside 2001:db8::/48, the first /56 begins at 2001:db8::. The following /60 begins at 2001:db8:0:100::, with remaining addresses represented as aligned CIDR blocks.
Good to know
Offline arithmetic, not scanning, reachability or assignment permission. Pure hexadecimal notation only; no embedded dotted IPv4 or zone identifiers. No IPv6 broadcast subtraction.
Reference: IETF RFC 5952: canonical IPv6 text (opens in a new tab) ↗
A prefix determines an exact address count
IPv6 blocks can exceed the exact-integer capacity of ordinary floating-point numbers. This page uses 128-bit integer arithmetic and displays counts as decimal text.
The first and last addresses describe arithmetic endpoints. They do not establish which addresses a network policy or device configuration can assign.
The ipv4 vlsm subnet planner calculator adds plan largest-first variable IPv4 subnet blocks from host demands, with exact alignment, explicit /31 and /32 interpretation and remaining CIDRs.
Largest-first requests avoid silent fragmentation
Requests are ordered by descending block size, with input order preserved for equal sizes. Every allocated start is aligned to the child’s size and stays within the parent.
All requested children must fit. The tool reports an input error rather than silently dropping a request and presenting a partial plan as complete.
Canonical text is a representation rule
Output uses lowercase hexadecimal and compresses the leftmost longest qualifying zero run. A shorter string does not change the underlying 128-bit address.
The normalized parent is displayed explicitly when entered host bits are cleared. Remaining space is decomposed into aligned CIDRs, rather than reported as an arbitrary unaligned address interval only.
Use the result with the next measurement
The IPv4 VLSM subnet planner calculator converts host demands into IPv4 blocks under an explicit reserved-address convention. IPv6 prefix allocation does not reuse its broadcast rules.
Offline arithmetic, not scanning, reachability or assignment permission. Pure hexadecimal notation only; no embedded dotted IPv4 or zone identifiers. No IPv6 broadcast subtraction.
A few questions, answered
Are large address counts rounded?
No, counts use exact BigInt arithmetic.
Is broadcast removed?
No, IPv6 has no IPv4-style broadcast deduction.
Does the tool contact the network?
No, it is entirely local arithmetic.