Two Subnets Overlap
Intermediate TroubleshootQuestion
A network engineer assigned 10.0.0.0/23 to the Sales VLAN and 10.0.1.0/24 to the Engineering VLAN. Devices on Engineering cannot reliably communicate with each other. Identify whether the subnets overlap, what the overlapping range is, and how to fix it.
Given
{
"subnet_a": "10.0.0.0/23",
"subnet_b": "10.0.1.0/24"
}
Answer
{
"overlap": true,
"subnet_a_range": "10.0.0.0 - 10.0.1.255",
"subnet_b_range": "10.0.1.0 - 10.0.1.255",
"overlap_range": "10.0.1.0 - 10.0.1.255",
"overlap_size": 256,
"fix": "Renumber Engineering VLAN to a non-overlapping block, e.g. 10.0.2.0/24"
}
Try to solve it first, then click Reveal Answer
Step-by-Step Explanation
Step 1: Expand both subnets to their full ranges
Sales VLAN — 10.0.0.0/23: - /23 = 512 addresses (2^9) - Network: 10.0.0.0 - Broadcast: 10.0.1.255 - Full range: 10.0.0.0 – 10.0.1.255
Engineering VLAN — 10.0.1.0/24: - /24 = 256 addresses (2^8) - Network: 10.0.1.0 - Broadcast: 10.0.1.255 - Full range: 10.0.1.0 – 10.0.1.255
Step 2: Check for overlap
Sales range: 10.0.0.0 – 10.0.1.255 Engineering range: 10.0.1.0 – 10.0.1.255
The Engineering subnet (10.0.1.0/24) is entirely contained within the Sales subnet (10.0.0.0/23). Overlap: 10.0.1.0 – 10.0.1.255 (256 addresses).
Step 3: Why this causes problems
Routers and Layer-3 switches use the most specific (longest prefix) match. When a packet destined for 10.0.1.50 arrives at the router:
- 10.0.0.0/23 matches (less specific, 23-bit prefix)
- 10.0.1.0/24 matches (more specific, 24-bit prefix) ← wins
The /24 route "wins" over the /23 for addresses in the overlap range. Devices configured with the /23 mask believe hosts in 10.0.1.x are on-link (same subnet), so they ARP directly instead of routing. This creates asymmetric paths and intermittent failures.
Step 4: Fix the overlap
Option A — Renumber Engineering:
Engineering VLAN: 10.0.2.0/24 (first non-overlapping /24 after Sales)
Option B — Resize Sales to /24:
Sales VLAN: 10.0.0.0/24 (shrink from /23 to /24)
Engineering VLAN: 10.0.1.0/24 (now non-overlapping)
Option A is usually safer as it avoids renumbering a large existing VLAN.
Step 5: Verification after fix
# On a router, check for duplicate routes
show ip route 10.0.0.0
show ip route 10.0.1.0
show ip route 10.0.2.0
# Each should point to a different interface/VLAN
# Ping from Engineering device to Sales device
ping 10.0.0.50 source 10.0.2.50
Quick overlap detection formula
Two subnets A and B overlap if: - A's network address is within B's range, OR - B's network address is within A's range
In CIDR terms: overlap exists if one prefix is a sub-prefix of the other (same leading bits, different length).