Network and IP Planning · #06
Online Subnet Overlap Checker
Lists overlaps within the same VRF and deliberate reuse across VRFs separately.
- Data is processed in your browser and not sent to a server
- Export: CSV
Tool
What does this tool do?
Branch roll-outs, mergers and VPNs often fail because the same address block is used in two places. A /25 defined elsewhere inside a /24 leads to unexpected route selection. Using the same block in different VRFs, however, is often a deliberate design. The tool separates the two cases.
How to use it
- Write
Label; CIDR; VRFon each line. If the VRF is empty, the default VRF field is used. - Press Calculate. Red rows are overlaps in the same VRF, yellow rows are reuse in different VRFs.
Fields
- Subnet list
- One per line: Label; CIDR; VRF (opt.). A bare CIDR is also accepted. Up to 2,000 lines.
- Default VRF
- Lines without a VRF are counted in this VRF.
Worked example
| Input | Value |
|---|---|
| Subnet list | |
Expected result: Office ⊃ Printers (same VRF, containment); Office and Guest share addresses in different VRFs (reuse); Store and Store-2 are adjacent and do not overlap; OT reuses Store/Store-2 space in another VRF.
The printer network is defined inside the office network, so two interfaces in the same VRF claim these addresses: an error to fix. Guest and OT are in separate VRFs and may be by design; check them again if routes are leaked between VRFs or NAT is used.
Method and assumptions
Each line is reduced to its network address and compared as a [first, last] range. Identical ranges are 'exact match', one inside the other is 'containment', no common address is 'no overlap'. Adjacent blocks (10.0.0.0/25 and 10.0.0.128/25) do not overlap.
Pairs are compared within the same address family. A different VRF is counted separately as 'reuse'.
Using the result and troubleshooting
Red rows state which block is wider; usually the narrower block should move or the wider one should be split. The VLAN and VLSM IP Planner can produce a new layout.
Assess yellow rows together with inter-VRF route leaking, shared-services VRFs or NAT.
Limits and common mistakes
- It compares the inventory you enter; it does not check what is actually configured.
- Lines with host bits set are converted to the network address.
Frequently asked questions
Is the same block in different VRFs an error?
No; it is normal in L3VPN and multi-tenant designs. Problems start when those VRFs meet in one routing table.
Related tools and service
- VLAN and VLSM IP PlannerSplits one parent block into several VLANs; returns subnet, gateway, DHCP range and spare capacity per VLAN, with XLSX export.
- CIDR AggregatorReduces a CIDR list to the smallest number of prefixes that cover exactly the same addresses.
Related service: VLAN, Routing and Network Segmentation