IPv6 Subnet & Prefix Allocation Planner
IPv6 Subnet & Prefix Allocation Planner: Borrows 2 bits (56 + 2 = /58), creating 4 non-overlapping /58 subnet blocks.
About this ipv6 subnet & prefix allocation planner
IPv6 Subnet & Prefix Allocation Planner — browser-based utility.
How this tool works
Implements client-side IPv6 Subnet & Prefix Allocation Planner operations. Borrows 2 bits (56 + 2 = /58), creating 4 non-overlapping /58 subnet blocks specifically designed for an enterprise network architect plans subnets across 4 company branch offices from a /56 prefix.
- Binary Bitmask Ingestion: Converts decimal dotted-quad IPv4 strings or hexadecimal colon-separated IPv6 strings into binary bit vectors.
- Bitwise Boolean Algebra: Performs bitwise AND, OR, and NOT operations between IP address integers and CIDR prefix masks.
- Address Class & Scope Tagging: Identifies RFC 1918 private ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), loopback, CGNAT, and multicast blocks.
- Subnet Topology Formatting: Renders network ID, usable host range, broadcast address, binary representation, and Cisco wildcard mask.
Worked example
Scenario: Divide one documentation IPv6 /56 into four equal local prefixes.
Sample input:
Processing: Borrow two bits and enumerate the first four /58 prefix starts.
Illustrative output:
Limits and verification
Enforces strict IPv4 prefix boundaries (/0 to /32) and IPv6 boundaries (/0 to /128). In RFC 3021 /31 subnets, correctly reports 2 usable point-to-point hosts without traditional network and broadcast exclusions.
Examples demonstrate an expected workflow; they do not prove every input or every branch of an external specification. Check important results with an independent source before using them for money, security, compliance, safety, or irreversible file changes.
Browser processing boundary
Tool input is processed by code running in the browser and is not intentionally sent to a CZOA processing API. The page can still request ordinary site assets, analytics, or advertising when those services are enabled. Browser extensions and managed-device software remain outside this tool's control.
Relevant references
These references govern or help explain the format, protocol, or calculation used here. Listing a reference does not claim certification or complete implementation of every optional feature.
- RFC 791 (Internet Protocol: IPv4)
- RFC 4632 (Classless Inter-domain Routing: CIDR)
- RFC 4291 (IP Version 6 Addressing Architecture)
Content owner: CZOA Tools · Last reviewed: 2026-09-15 · Review methodology
How to use it
- Enter, paste, or select your input data into the IPv6 Subnet & Prefix Allocation Planner workspace controls.
- Review available parameter fields, units, formats, or options configured for your task.
- Click the action button or observe immediate live calculations rendered in your browser runtime.
- Inspect the resulting output and any diagnostic messages, then copy or download the result if needed.
Frequently asked questions
What does the IPv6 planner calculate?+
It accepts CIDR text or JSON containing cidr and subnets/count. It masks the address to the allocated prefix, borrows ceil(log2(requestedSubnets)) bits, and emits exactly the requested number of equally sized subnet prefixes from the start of that allocation. It does not allocate addresses on a network.
Which inputs and limits apply?+
The requested count must be an integer from 1 through 65536. The prefix must be an integer from 0 through 128 and the computed subnet prefix cannot exceed 128. JSON uses cidr or prefix plus subnets or count; plain CIDR defaults to two subnets. Invalid JSON, a non-IPv6 address, invalid prefix, count, or exhausted space produces an error.
How are non-power-of-two counts handled?+
The tool borrows enough bits for the next power of two but returns only the requested first N subnets. For /56 with count 4 it borrows 2 bits and returns four /58 prefixes: 2001:db8:1000::/58, :40::/58, :80::/58 and :c0::/58. A count of 3 also uses two borrowed bits and leaves one possible /58 unlisted.
What result does the worked example produce?+
In the worked example, the tool exactly matched an independently calculated JSON vector for 2001:db8:1000::/56 and four subnets. The first example used an incorrect :400:: expectation and failed; the corrected canonical IPv6 /58 sequence matched. Network requests observed during the example had no submitted CIDR payload, which describes that run only.