Why the first and last address in a subnet are off limits

In any subnet, the first address is reserved as the network address and the last is reserved as the broadcast address. Neither can be assigned to a host. Understanding why these addresses are off limits is fundamental to subnetting and critical for accurate capacity planning in your network design.

The network address: identifying the subnet

The network address is the first usable address in a subnet block. It is derived by setting all host bits to zero while keeping the network portion intact. This address serves as the identifier for the entire subnet and is used by routers to determine which subnet a destination belongs to.

For example, in the subnet 192.168.1.0 divided by 24, the network address is 192.168.1.0. The slash-24 notation means the first 24 bits identify the network, and the remaining 8 bits are available for host addresses. Because the network address itself has all host bits set to zero, it cannot be assigned to any individual device.

Subnet: 192.168.1.0/24
Network address: 192.168.1.0 (all host bits = 0)
First usable host: 192.168.1.1
Last usable host: 192.168.1.254
Broadcast address: 192.168.1.255 (all host bits = 1)

The broadcast address: reaching all hosts

The broadcast address is the last address in a subnet block. It is created by setting all host bits to one. When a device sends a packet to the broadcast address, the packet is delivered to every host on that subnet. This is essential for protocols like DHCP and ARP, but the broadcast address itself cannot be assigned to a host interface.

In 192.168.1.0/24, the broadcast address is 192.168.1.255. If you attempt to configure a host with this address, the device will treat outbound traffic as broadcast frames, breaking normal unicast communication and causing routing and application failures.

Impact on usable address count

The reservation of network and broadcast addresses reduces the number of usable host addresses in a subnet. A /24 subnet contains 256 total addresses (2 raised to the power of 8), but only 254 are usable for hosts.

• →Total addresses in /24: 256
• →Network address (reserved): 1
• →Broadcast address (reserved): 1
• →Usable host addresses: 254

This overhead becomes more significant in smaller subnets. A /30 subnet (used for point-to-point links) has only 4 addresses total, leaving just 2 usable addresses for the two ends of the link. A /31 subnet is a special case defined in RFC 3021 that eliminates this overhead for point-to-point use by treating the subnet as having no network or broadcast address, allowing both addresses to be used.

Practical implications for network design

When planning subnets for your network, always account for the loss of two addresses. If you need to support 100 hosts, you cannot use a /25 subnet (which provides only 126 usable addresses); you must use a /24 (254 usable addresses). Miscalculating this overhead can lead to address exhaustion and require costly network redesign.

Additionally, some network automation tools and configuration generators may fail silently if you attempt to assign the network or broadcast address to a device. Always verify subnet calculations before deployment, and use tools that enforce these rules during design.