VLSM Allocation Leaves Unaddressed Gap
Advanced TroubleshootQuestion
A network has been allocated 10.0.0.0/24. Two subnets have been assigned: LAN at 10.0.0.0/25 and Servers at 10.0.0.192/26. A junior engineer reports that addresses between the two allocations are missing from the address plan. Identify the gap, its size, and how it can be used.
Given
{
"network": "10.0.0.0/24",
"allocations": [
{
"subnet": "10.0.0.0/25",
"name": "LAN"
},
{
"subnet": "10.0.0.192/26",
"name": "Servers"
}
]
}
Answer
{
"lan_range": "10.0.0.0 - 10.0.0.127",
"servers_range": "10.0.0.192 - 10.0.0.255",
"gap": "10.0.0.128/26",
"gap_range": "10.0.0.128 - 10.0.0.191",
"gap_size": 64,
"gap_usable": 62,
"problem": "64 addresses (10.0.0.128-10.0.0.191) are unallocated between LAN and Servers"
}
Try to solve it first, then click Reveal Answer
Step-by-Step Explanation
Step 1: Map out the two existing allocations
LAN — 10.0.0.0/25: - /25 = 128 addresses - Range: 10.0.0.0 – 10.0.0.127 - Ends at: 10.0.0.127
Servers — 10.0.0.192/26: - /26 = 64 addresses - Range: 10.0.0.192 – 10.0.0.255 - Starts at: 10.0.0.192
Step 2: Find the gap
10.0.0.0/25 → 10.0.0.0 to 10.0.0.127 (LAN)
╔═══════════╗
║ GAP! ║
╚═══════════╝
10.0.0.128 to 10.0.0.191 (unallocated)
10.0.0.192/26 → 10.0.0.192 to 10.0.0.255 (Servers)
Gap: 10.0.0.128 – 10.0.0.191 = 64 addresses = one /26 block.
CIDR for the gap: 10.0.0.128/26
Step 3: Verify the gap is a valid CIDR block
10.0.0.128 ÷ 64 = 2 → aligned to /26 boundary (must be a multiple of 64) ✓ This is a clean, allocatable /26 block.
Step 4: How the gap was created
The address plan was likely written in this order: 1. Allocated LAN: 10.0.0.0/25 (128 addresses, ends at .127) 2. Allocated Servers: 10.0.0.192/26 — possibly intended to start at the "last" /26 of the /24
The space between them (.128–.191) was never explicitly allocated.
Step 5: Use the gap
Options for the unallocated /26:
| Use | Subnet | Notes |
|---|---|---|
| DMZ | 10.0.0.128/26 | Web/mail servers, public-facing |
| Management | 10.0.0.128/26 | Network equipment management |
| Future expansion | 10.0.0.128/26 | Reserve for growth |
| Split into /27s | 10.0.0.128/27 + 10.0.0.160/27 | Two smaller segments |
Step 6: Update the address plan
Revised allocation table:
| Subnet | Name | Usable | Status |
|---|---|---|---|
| 10.0.0.0/25 | LAN | 126 | Allocated |
| 10.0.0.128/26 | DMZ (new) | 62 | Fill the gap |
| 10.0.0.192/26 | Servers | 62 | Allocated |
The entire 10.0.0.0/24 is now cleanly accounted for.
Key lesson
Always document your VLSM allocations in a spreadsheet or IPAM tool that shows: - Start address - End address - Next free address
Tools like NetBox, phpIPAM, or even a simple table catch gaps before they become orphaned address space.