IPv4 Subnet Split and VLSM Planner
Split an IPv4 network into N equal subnets or allocate boundary-aligned VLSM blocks by required host count with CSV and Markdown export.
Input Parameters
Calculation Results
- parentCidr
- 192.168.10.0/24
- parentNetwork
- 192.168.10.0
- parentBroadcast
- 192.168.10.255
- parentTotalAddresses
- 256
- mode
- vlsm
- allocatedAddresses
- 228
- unallocatedAddresses
- 28
| # | Name | Subnet | Host Range | Usable | Unused |
|---|---|---|---|---|---|
| 1 | Staff | 192.168.10.0/25 | 192.168.10.1 โ 192.168.10.126 | 126 | 26 |
| 2 | Voice | 192.168.10.128/26 | 192.168.10.129 โ 192.168.10.190 | 62 | 12 |
| 3 | CCTV | 192.168.10.192/27 | 192.168.10.193 โ 192.168.10.222 | 30 | 5 |
| 4 | WAN | 192.168.10.224/30 | 192.168.10.225 โ 192.168.10.226 | 2 | 0 |
How to Use This Tool
- Enter the parent network block in CIDR notation (e.g. 192.168.10.0/24 or 10.10.0.0/16) and select either Mode B (VLSM by host count) or Mode A (Split into N equal subnets).
- In VLSM mode, enter your segment host counts (e.g. Staff:100, Voice:50, CCTV:25, WAN:2); in Equal Split mode, specify the target number of equal subnets N.
- Inspect the generated subnet table showing each CIDR block, usable host range, usable count, and unused space, then export the plan as CSV or Markdown.
Worked Example: VLSM 4 VLANs (192.168.10.0/24)
Splitting parent network 192.168.10.0/24 (256 addresses) for Staff (100 hosts), Voice (50 hosts), CCTV (25 hosts), and WAN (2 hosts) allocates 4 boundary-aligned blocks: 192.168.10.0/25 (126 usable), 192.168.10.128/26 (62 usable), 192.168.10.192/27 (30 usable), and 192.168.10.224/30 (2 usable), with 28 addresses left unallocated.
{
"network": "192.168.10.0/24",
"mode": "vlsm",
"requirements": "Staff:100, Voice:50, CCTV:25, WAN:2",
"splitCount": 4
}- parentCidr:
- 192.168.10.0/24
- parentNetwork:
- 192.168.10.0
- parentBroadcast:
- 192.168.10.255
- parentTotalAddresses:
- 256
- mode:
- vlsm
- allocatedAddresses:
- 228
- unallocatedAddresses:
- 28
Core Concept & Engineering Notes
How It Was Calculated (Formulas & Steps)
Mathematical Formulas
- Block Size = smallest 2^h where (2^h โ 2) โฅ Required Hosts (minimum 4 addresses /30)
- Child Prefix Length = 32 โ log2(Block Size)
- Aligned Start Address = ceil(Cursor / Block Size) ร Block Size
- Unused Hosts = Usable Hosts โ Required Hosts
- Utilization (%) = (Required Hosts รท Usable Hosts) ร 100%
Step-by-Step Calculation
- Mode B (VLSM): Parent network 192.168.10.0/24 (256 total addresses, 192.168.10.0 โ 192.168.10.255)
- Sorted 4 host requirements descending by block size: Staff (100 hosts โ /25, block 128), Voice (50 hosts โ /26, block 64), CCTV (25 hosts โ /27, block 32), WAN (2 hosts โ /30, block 4)
- Allocated 228 of 256 addresses (28 addresses remaining free)
Frequently Asked Questions (FAQ)
Why does VLSM always sort allocations from the largest host requirement to the smallest?
Every CIDR block must start on an IP address that is an exact multiple of its block size (for example, a 128-address /25 must start at .0 or .128). Allocating the largest blocks first guarantees that subsequent smaller blocks naturally align on binary boundaries without creating fragmented gaps.
What block size is allocated if I request exactly 30 hosts?
For 30 hosts, a /27 block (32 total addresses, 32 โ 2 = 30 usable addresses) satisfies the requirement with 0 unused addresses. If you want expansion headroom, request 35 or 40 hosts so the planner steps up to a /26 block (62 usable hosts).
How do I export the VLSM subnet table to Excel or Git documentation?
Click Export CSV on the result card to download a .csv file ready for Microsoft Excel or Google Sheets, or click Copy Markdown to paste a formatted table directly into your README.md or engineering wiki.
Related Calculators
Calculate IPv4 network address, broadcast, usable host range, netmask, wildcard, binary mask, and RFC address type (RFC 1918, /31, CGNAT).
Expand and compress IPv6 addresses per RFC 5952, calculate network prefix boundaries, /64 SLAAC subnet counts, and child prefix blocks.
Calculate Limit-At (CIR), Max-Limit (MIR), Burst, PCQ, and FQ-CoDel for RouterOS v7 with automated configuration script generation.
References & Notes
- RFC 4632 โ Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan
- RFC 1878 โ Variable Length Subnet Table For IPv4
- RFC 1918 โ Address Allocation for Private Internets
Note: Results above are mathematical estimates based on standard formulas. Always verify against official vendor documentation and site conditions before production deployment.