IPv4 Subnetting and CIDR Decision Shortcuts Quick Reference for Network+ N10-009

Subnetting questions often look like calculation problems, but most of them are really decision problems. You rarely need every fact about the subnet. You need one answer: the smallest prefix that fits, the block that contains an address, the network and broadcast boundaries, or whether two hosts are local to each other.

The full IPv4 Subnetting Reference teaches the complete method. This Quick Review is for recognizing the answer faster after you already understand that method.

1. Five subnetting decisions

2. High-value prefixes at a glance

For ordinary IPv4 subnets through /30, the traditional usable count is two less than the total address count because the network and broadcast addresses are reserved.

A one-bit prefix change halves or doubles the address count. Moving from /26 to /27 changes 64 total addresses into 32. Moving from /27 to /26 doubles the block back to 64.

For a prefix /n:

Host bits = 32 - n
Total addresses = 2^(host bits)

For ordinary subnets through /30:

Traditional usable hosts = total addresses - 2

/31 and /32 are special cases. Use the full subnetting reference when the question specifically tests point-to-point /31 behavior or host routes.

3. Choose the smallest subnet that actually fits

This is one of the fastest Network+ decisions once the thresholds are familiar.

The threshold matters more than the round number.

• 30 hosts fit in /27.
• 31 hosts do not. Move to /26.
• 62 hosts fit in /26.
• 63 hosts require /25.
• 126 hosts fit in /25.
• 127 hosts require /24.

If the scenario requires room for infrastructure or growth, include those addresses before selecting the prefix. Do not silently add capacity the question did not request.

4. Use block size to find a subnet quickly

Find the first mask octet that is not 255. That is the changing octet.

Block size = 256 - changing mask octet

For /27, the mask is 255.255.255.224:

256 - 224 = 32

The fourth-octet boundaries are:

0, 32, 64, 96, 128, 160, 192, 224

If the host is 192.168.10.173/27, 173 falls in the 160-191 block. You already know:

• Network: 192.168.10.160
• Broadcast: 192.168.10.191
• Traditional usable range: 192.168.10.161-190

The same shortcut works when the changing octet is not the fourth octet.

For /20, the mask is 255.255.240.0:

256 - 240 = 16

The third-octet boundaries are 0, 16, 32, 48, 64, and so on. Address 172.20.77.9/20 therefore belongs to the third-octet block 64-79, giving network 172.20.64.0/20.

5. Derive network, broadcast, and usable boundaries

Once you know the block, the rest follows.

For 10.20.37.200/27:

1. /27 means fourth-octet blocks of 32.
2. Nearby boundaries are 192 and 224.
3. The network address is the lower boundary: 10.20.37.192.
4. The broadcast address is one less than the next boundary: 10.20.37.223.
5. The traditional usable range is 10.20.37.193-222.

Do not calculate the usable range before the network and broadcast boundaries. That is how off-by-one errors sneak in.

A host address can be numerically between two other host addresses and still belong to a different subnet when a boundary falls between them. The prefix decides the boundary.

6. Decide whether two hosts are local to each other

Two IPv4 hosts with the same prefix length are in the same subnet when their addresses resolve to the same network boundary.

Consider:

192.168.10.62/26
192.168.10.65/26

A /26 uses blocks of 64:

0-63
64-127
128-191
192-255

.62 belongs to the first block. .65 belongs to the second. They are in different /26 subnets and normally need Layer 3 forwarding to communicate.

Change both hosts to /25:

192.168.10.62/25
192.168.10.65/25

A /25 uses blocks 0-127 and 128-255. Both addresses now land in the same subnet.

When hosts use different masks, do not assume they agree about what is local. Each host applies its own mask to make its own local-versus-remote decision. A mask mismatch can create one-way or confusing connectivity even when the addresses look close.

7. Use VLSM by sizing the largest requirement first

Variable Length Subnet Masking (VLSM) lets one parent network contain subnets of different sizes. The safest allocation routine is:

1. List the required host counts.
2. Convert each requirement to the smallest fitting prefix.
3. Allocate the largest block first.
4. Start each subnet on a valid boundary for its prefix.
5. Continue with the next largest block.
6. Confirm that no ranges overlap.

Suppose 192.168.50.0/24 must support:

• 100 hosts
• 50 hosts
• 20 hosts

The smallest common fits are:

• 100 hosts -> /25 with 126 traditional usable addresses
• 50 hosts -> /26 with 62
• 20 hosts -> /27 with 30

One valid layout is:

192.168.50.0/25     addresses 0-127
192.168.50.128/26   addresses 128-191
192.168.50.192/27   addresses 192-223

The remaining 192.168.50.224/27 block is still available.

Allocating the 20-host subnet first may leave fragments that cannot fit the later 100-host requirement. Largest-first allocation reduces that risk.

8. Recognize special IPv4 clues without changing the subnet math

Address category and subnet boundary are separate decisions.

A private address can still be subnetted with /26, /20, or any other valid prefix. "Private" describes the address category, not the size of the local subnet.

9. Scenario comparisons

A VLAN needs 55 usable IPv4 addresses

Choose /26. It provides 64 total addresses and 62 traditional usable addresses. /27 provides only 30. /25 would work, but it is larger than required.

Host 192.168.40.77/26 needs its network address

A /26 has a block size of 64. Fourth-octet boundaries are 0, 64, 128, and 192. Address 77 lands in the 64-127 block, so the network is 192.168.40.64/26.

Two hosts are 10.5.8.126/25 and 10.5.8.129/25

A /25 divides the fourth octet into 0-127 and 128-255. The hosts are on different subnets.

A /24 must be divided for 100, 40, and 10 hosts

Size largest first:

• 100 -> /25
• 40 -> /26
• 10 -> /28

Allocate the /25 first, then /26, then /28, each on a valid boundary. Do not cut small blocks out of the parent before reserving space for the largest requirement.

A workstation shows 169.254.44.18

Recognize the IPv4 link-local clue before doing unrelated subnet math. If the workstation was expected to use DHCP, investigate the client, VLAN, relay, server, pool, and path. Use the DHCP, DNS, SLAAC, and Time Services Quick Reference for that service decision.

10. Common exam traps

• Subtracting two addresses before identifying the subnet boundary.
• Assuming matching first three octets means two hosts share a subnet.
• Choosing a subnet that has enough total addresses but not enough traditional usable host addresses.
• Choosing the largest subnet that works when the question asks for the smallest fit.
• Forgetting that the prefix determines the changing octet.
• Treating 172.0.0.0/8 as private instead of the actual 172.16.0.0/12 RFC 1918 range.
• Allocating small VLSM blocks first and leaving no aligned space for a larger requirement.
• Using the default route or route metric to answer a subnet-boundary question.
• Treating a 169.254.0.0/16 address as proof that the cable is bad. It points toward failed normal address configuration, not one guaranteed root cause.
• Applying the ordinary network-and-broadcast subtraction to /31 without recognizing the point-to-point special case.

11. Rapid review grid

12. Official references

• CompTIA Network+ certification page
• RFC 4632: Classless Inter-domain Routing
• RFC 1918: Address Allocation for Private Internets
• RFC 3927: Dynamic Configuration of IPv4 Link-Local Addresses
• RFC 3021: Using 31-Bit Prefixes on IPv4 Point-to-Point Links