Overlapping VLSM Subnets – Speed Test 2
Time for another practice problem to find any overlapping IPv4 subnets. I’ve kicked this one up a notch compared to the previous exercise – this time the list (below the fold) shows IP addresses and prefixes. You have to first calculate the subnet IDs, and then figure out where (if any) the overlaps exist.
If you’re not sure what to do, look at the following post first, which puts it in perspective, and then come back here for the problem and the speed challenge. Here’s a complete list of related posts:
The list shows IP addresses and masks. Derive the subnet IDs, and then identify which subnets overlap with each other. That is, if the subnets listed as #1 and #2 in the list overlap, list “1&2” as your answer.
- 9.200.204.208/23
- 9.204.200.208/26
- 9.209.209.201/26
- 9.205.201.209/24
- 9.201.205.209/25
[…] answer for Overlapping VLSM Subnets Speed Test 2 are below the fold! Here’s a complete list of related […]
answer is: none…
1) 9.200.204.208/23
9.200.1100110-0.00000000 9.200.204.0/23 9.200.1100110-1.11111111 9.200.205.255/23
5) 9.201.205.209/25
9.201.11001101.0-0000000 9.201.205.0/25 9.201.11001101.0-1111111 9.201.205.127/25
2) 9.204.200.208/26
9.204.11000100.00-000000 9.204.200.0/26 9.204.11000100.00-111111 9.204.200.63/26
4) 9.205.201.209/24
9.205.11000101.-00000000 9.205.201.0/24 9.205.11000101.-11111111 9.205.201.255/24
3) 9.209.209.201/26
9.209.11001101.00-000000 9.209.209.0/26 9.209.11001101.00-111111 9.209.209.63/26
Because regardless of what happens with the networks, the second octet no coincidence.