Once the fundamentals of IPv4 addressing are understood, the next step is to apply these concepts to real-world network design. Subnetting is the core technique that transforms a single, flat address space into a structured hierarchy of smaller networks, each tailored to specific organizational needs. This lesson focuses on the practical mechanics of subnetting — calculating network addresses, broadcast addresses, and valid host ranges — as well as assessing allocation efficiency, designing addressing plans, and diagnosing the configuration errors that most commonly break end-to-end connectivity.

The Mechanics of Subnetting

Subnetting works by borrowing bits from the host portion of an IPv4 address and reassigning them to the network portion. Each borrowed bit doubles the number of available subnets while halving the number of hosts per subnet. The fundamental formulas are 2:

$\text{Number of subnets} = 2^s$

$\text{Number of usable hosts per subnet} = 2^h - 2$

Where $s$ is the number of bits borrowed for subnetting and $h$ is the number of remaining host bits. The subtraction of 2 accounts for the reserved network address (all host bits = 0) and broadcast address (all host bits = 1), neither of which can be assigned to a device .

The Subnet Increment (Block Size)

The block size is the key to quickly identifying subnet boundaries without converting every address to binary:

$\text{Block size} = 256 - \text{(value of the interesting octet in the subnet mask)}$

For example, with a mask of 255.255.255.192 (i.e., /26), the interesting octet is 192:

$\text{Block size} = 256 - 192 = 64$

This means subnets start at multiples of 64 in the last octet: .0, .64, .128, .192.

Address Allocation Efficiency: FLSM vs. VLSM

A critical challenge in network design is assigning address space without excessive waste. Two approaches exist 2:

Fixed-Length Subnet Masking (FLSM) applies the same subnet mask to every subnet in the network. This is simple to manage but inherently wasteful: if a network has departments needing 100, 50, 20, and 2 hosts respectively, FLSM would allocate a /25 (126 usable hosts) to every subnet — wasting over 60% of addresses in the smallest subnets.

Variable-Length Subnet Masking (VLSM) solves this by allowing each subnet to have a different prefix length. The VLSM process always starts by allocating the largest subnet first from the available address block, then carving the next-largest from the remaining space, and so on.

VLSM reduces wasted addresses by approximately 85% compared to FLSM in this scenario .

Selecting IPv4 Addressing Plans for Network Topologies

When designing an addressing plan for a small or medium-sized network, several practical principles guide the decision:

1. Start with Requirements Gathering: Determine the number of subnets needed and the maximum host count per subnet. Include separate subnets for servers, user VLANs, management networks, and point-to-point WAN links.
2. Choose the Right Private Block: Select an RFC 1918 range that provides sufficient room for growth. A /16 block (e.g., 172.16.0.0/16) gives 65,534 addresses — enough for most medium enterprises.
3. Apply VLSM for Efficiency: Use VLSM to right-size each subnet. Assign the largest subnets first and work downward.
4. Reserve Address Space for Growth: Allocate no more than 50–60% of a block initially. Reserve the remaining space for future expansion to avoid costly re-addressing.
5. Assign Consistent Host Addresses: Use a convention for key infrastructure: for example, .1 for the default gateway, .2–.10 for servers, .11–.20 for printers, and DHCP pools starting from .100 upward.
6. Document Everything: Maintain an IP Address Management (IPAM) spreadsheet or tool that maps every subnet, its purpose, VLAN association, gateway address, and DHCP range .

Diagnosing Common IPv4 Addressing Errors

Misconfigured IPv4 settings are among the most frequent causes of connectivity failures. The following errors represent the vast majority of addressing issues encountered in practice 2:

1. Incorrect Subnet Mask

If two hosts on the same physical network are configured with different subnet masks, one host may believe the other is on a remote network and attempt to send traffic to the default gateway instead of communicating directly. For example:

• Host A: 192.168.1.50/24 → Network = 192.168.1.0
• Host B: 192.168.1.100/16 → Network = 192.168.0.0

Host B sees Host A as a local neighbor. But Host A sees Host B as local too. However, if the masks were reversed (Host A with /16, Host B with /24), Host A would see Host B's network as 192.168.0.0 and attempt local delivery, while Host B sees Host A's network as 192.168.1.0 and also attempts local delivery — the mismatch can cause intermittent or asymmetric failures that are extremely difficult to debug.

2. Duplicate IP Address

When two devices are assigned the same IPv4 address, an IP conflict occurs. Both devices will experience intermittent connectivity as ARP tables flip between the two MAC addresses. Most modern operating systems detect and warn about this condition.

3. Wrong Default Gateway

If a host's default gateway address does not match the router's interface IP on that subnet, the host can communicate locally but cannot reach any remote network. This is the classic "I can ping my neighbor but not the internet" symptom.

4. Host Assigned a Network or Broadcast Address

Accidentally assigning the network address (e.g., 192.168.1.0/24) or broadcast address (e.g., 192.168.1.255/24) to a device renders it unable to communicate, since these addresses are reserved for protocol-level use.