AP Networking Subnetting Guide

A subnet mask is not just math—it tells a host when a router is needed

Subnetting becomes much easier when every calculation answers a networking question. The prefix separates the network portion of an IPv4 address from the host portion. That boundary tells an endpoint whether a destination belongs to its own IP subnet or must normally be sent toward a default gateway.

Before moving to a mixed exam, test whether you can apply subnet boundaries inside a larger failure scenario. The AP Networking IP Addressing and Subnetting Practice Test includes 75 explained items that connect network identifiers, broadcast addresses, gateway placement, and nonoverlapping allocation.

Suppose a host is 192.168.50.70/27. The /27 creates blocks of 32 addresses in the final octet: 0–31, 32–63, 64–95, 96–127, and so on. The host belongs to 192.168.50.64/27. A destination at 192.168.50.90 is local. A destination at 192.168.50.100 is not. The addresses look similar in decimal, but the prefix—not visual similarity—controls the decision.

That decision changes the packet path. For a local IPv4 destination, the sender can resolve the destination's local Layer 2 address. For a remote destination, the sender normally resolves the Layer 2 address of its default gateway and sends the frame there while keeping the remote IP as the Layer 3 destination. This is why subnetting belongs in troubleshooting, routing, VLAN design, DHCP, and security—not only on calculation worksheets.

Use the same five steps for network, broadcast, host range, and locality

Block size is fast; binary explains why it works

IPv4 addresses contain 32 bits. A /26 says the first 26 bits are network bits and the remaining 6 are host bits. In the final octet, the /26 mask is 11000000, decimal 192. The host value 141 is 10001101. A bitwise AND preserves only the network bits:

The result is the same network boundary found with the block-size shortcut. Understanding both methods is useful: block size is efficient for common hand calculations, while binary explains prefixes that cross a different octet and helps prevent memorized tricks from becoming detached from the actual address logic.

The subnet calculation changes who receives the Ethernet frame

For IPv4 communication on an Ethernet LAN, the endpoint first decides whether the destination IP is local according to its own configured prefix. If local, it can resolve the destination's MAC address and send directly at Layer 2. If remote, it normally resolves the default gateway's MAC address and sends the frame to the router. The remote IP remains the packet destination.

This distinction explains why a wrong mask can be so deceptive. A host with a mask that is too wide may believe a remote address is local. It can repeatedly try to resolve that destination on the local link rather than use the gateway. A mask that is too narrow can make a truly local peer appear remote, pushing traffic toward a gateway unnecessarily. Whether communication actually fails can depend on router behavior and topology, so the wrong mask does not guarantee one universal symptom.

That last point is important for troubleshooting: configuration errors produce behavior through mechanisms. Do not memorize “wrong mask = no Internet.” Instead, calculate how the incorrect prefix changes the local/remote classification for the specific destination in the scenario. Continue with Wrong Subnet Mask Symptoms for failure cases.

A DHCP scope is an address plan, not merely a pool of numbers

A DHCP scope should supply clients with configuration appropriate for the intended subnet: usable addresses from the correct range, the correct prefix or mask, a reachable default gateway, and relevant options such as DNS servers. If the scope boundary is wrong, the server can hand out addresses that look valid but do not belong to the intended Layer 3 design.

For example, a /27 LAN at 10.50.4.64/27 has a traditional usable range of .65–.94. A pool that accidentally leases .100 is crossing into the next /27 block. A gateway option of .65 could be valid; .97 would not be in the same /27. Subnetting therefore gives you a way to audit DHCP artifacts instead of merely asking whether the client “got an IP.”

This also helps distinguish DHCP failure from later dependencies. If a client receives a valid address, correct /27 mask, local gateway, and appropriate DNS configuration, that is useful evidence about configuration delivery. It does not prove routing, DNS service health, or application reachability. Review the dependency in DHCP Explained.

The same prefix logic you use for hosts is used to describe route destinations

A route such as 10.20.30.0/24 represents a destination prefix. A router compares the destination IP with available routes and prefers the most specific matching prefix. If the same destination matches a /8, /16, /24, and /27, the /27 is the longest and therefore the most specific match.

Subnetting skill makes routing tables readable. Instead of seeing prefixes as labels, you can determine exactly which destination range each route covers. You can also detect overlap: a broader route can cover many networks while a narrower route carves out a more specific path. The default route 0.0.0.0/0 is the least specific IPv4 route and is used only when no more specific match wins.

Do not confuse route selection with path success. A router can select the mathematically correct prefix while the next hop is unreachable, an interface is down, a firewall blocks the flow, or the return route is missing. Practice that distinction with Routing Table Analysis Practice.

Three short cases that combine subnet math with network reasoning

Once these feel automatic, use Subnetting Practice Questions and the Subnetting Calculator With Steps. The calculator is most useful as an answer checker after you have committed to your own boundary.

Apply subnetting where the boundary actually matters