CompTIA N10-009: Subnetting Without Memorization
Subnetting is a way to describe address boundaries, not a speed contest involving memorized tables. An IPv4 prefix length identifies the leading bits shared by addresses within one subnet; the remaining bits vary. From that structure, a technician can derive the network address, the conventional broadcast address, the address count and the most-specific route matching a destination. Once the boundaries are visible, common DHCP and routing errors become easier to explain. Memorized patterns are useful as checks, but the underlying binary relationship is what transfers to unfamiliar prefix lengths.
On this page
The CompTIA Network+ N10-009 exam includes IPv4 addressing and implementation as applied skills. In enterprise network engineering, address planning is connected to VLANs, gateways, route aggregation, ACLs, VPN overlap and monitoring. A technician needs to distinguish a subnet that is mathematically correct from one that is operationally appropriate for the users, services and future expansion it must support.
Treat prefix length as a boundary
IPv4 addresses contain 32 bits. A /24 indicates that 24 leading bits describe the network, leaving eight bits that can vary. That gives 256 total addresses in the block. A /26 leaves six host bits, giving 64 addresses, and a /27 leaves five, giving 32. In most ordinary IPv4 subnets, the all-zero host address identifies the network and the all-one host address is the directed broadcast address, leaving two fewer conventional usable host addresses. Point-to-point and special addressing arrangements may follow different conventions and should not be forced into that rule.
The dotted-decimal mask is another way to represent the same boundary. A /26 uses 255.255.255.192, because the final octet begins with two network bits set to one. Understanding the bit pattern makes it possible to derive an unfamiliar mask without guessing. A /28, for example, has four host bits and therefore 16 addresses per aligned block.
Find the network with block size
In the octet where a mask changes between all network bits and host bits, the block size is 256 minus the mask value for that octet. For 192.0.2.77/26, the final mask octet is 192, so the block size is 64. Final-octet blocks begin at 0, 64, 128 and 192. The address 77 falls in the 64–127 block: the network is 192.0.2.64/26, the broadcast is 192.0.2.127, and conventional usable hosts run from .65 through .126.
Always verify that calculation using the prefix, not only the last octet. A /20 changes the third octet and can cover many /24-sized ranges. When subnet calculations involve several octets, write the mask and find the changing octet first. That small discipline prevents the common error of treating every network as if the fourth octet contained the only meaningful boundary.
Separate address count from allocation policy
A subnet that technically accommodates 62 conventional IPv4 host addresses may still be too small for a VLAN expected to contain 60 clients plus network appliances, wireless infrastructure, transient devices and growth. Reserve capacity based on the service, lease duration and operational model. Document gateway reservations, DHCP exclusions and significant static allocations so address conflicts are not hidden within a pool that appears mathematically large enough.
The prefix also establishes a broadcast domain only when it is used consistently with the actual Layer 2 design. If clients have different masks on the same VLAN, one host may believe the destination is local and attempt ARP while another sends traffic to the gateway. A mismatch can look like intermittent application failure even when both devices have valid-looking addresses.
Use variable-length subnet masks deliberately
VLSM lets different subnets use different prefix lengths according to actual need. A branch network may allocate a larger prefix to employee clients, a smaller one to management interfaces and another to a point-to-point link. Begin with the largest requirements and allocate aligned, non-overlapping prefixes while preserving expansion space. Random allocations can make route summarization difficult and raise the cost of later mergers or VPN integrations.
Summarization depends on binary alignment. Two adjacent /25 prefixes can form a /24 summary only when their starting addresses align on a /24 boundary. A summary that is too broad may attract traffic to destinations the advertising site cannot actually reach. Document the component subnets and verify the entire summarized range before applying a routing change.
Use subnetting to diagnose real faults
When a workstation cannot reach a peer, write down both addresses and masks. Determine whether each endpoint considers the other local. A wrong mask may cause ARP requests for a destination that should be routed; a wrong gateway may break all off-subnet connectivity. If the local boundary is correct, examine routing, VLAN assignment, DHCP scope and firewall policy instead of recalculating the same prefix repeatedly.
An overlap can stay hidden until two sites are joined. Separate offices can both use 192.168.10.0/24 in isolation, but a straightforward site-to-site route cannot distinguish identically numbered remote and local networks. Renumbering or deliberately engineered translation may be required. A documented prefix inventory is therefore a preventive control, not merely administrative paperwork.
Relate address math to routing and services
The routing table selects the most-specific prefix matching a destination, so subnetting and forwarding are inseparable. A missing more-specific route can send traffic to a default gateway that is not intended to reach the destination. Conversely, a wrong DHCP mask can make a client choose local ARP when the router’s tables are perfectly correct. Diagnose client interpretation and router interpretation separately.
The supporting IPv4 subnetting explanation is useful for practising aligned blocks and VLSM. If the client has a correct address but a service name fails, investigate DNS resolution rather than assuming address calculation explains every symptom. Real incidents often cross layers, but the first failed stage should remain identifiable.
Build speed by verifying a few complete examples from both directions: derive the network from a host and prefix, then check whether that host falls within the calculated block and before the next boundary. Explain what the result means for routing, DHCP and access policy. The enduring skill is not a memorized number; it is the ability to identify where one network stops and another begins.