Subnet Calculator & CIDR Planner

In the early architecture of the ARPANET and early Internet, IPv4 addresses were divided into rigid classes: Class A (/8 with 16.7 million hosts), Class B (/16 with 65,534 hosts), and Class C (/24 with 254 hosts). By 1992, the explosive growth of connected organizations created two imminent existential threats to the Internet:

1. Massive Address Waste: Organizations that required 500 IP addresses could not fit into a Class C block, so they were allocated an entire Class B block (65,534 addresses), leaving more than 99% of their allocated address space stranded and unused.
2. Routing Table Explosion: Every individual classful network required an entry in the core BGP routing tables of global Internet routers. Routers of the era were running out of memory to store routing tables.

In September 1993, the Internet Engineering Task Force (IETF) published RFC 1519, introducing Classless Inter-Domain Routing (CIDR). CIDR eliminated the fixed boundary constraints of address classes. It introduced Variable-Length Subnet Masking (VLSM), allowing network engineers to slice IP address blocks into arbitrary prefix lengths (/25, /26, /27, /28) that matched their actual operational requirements. Furthermore, CIDR introduced Route Aggregation (Supernetting), enabling thousands of contiguous subnets to be summarized into a single route announcement, compressing the global BGP routing table.

In any standard IPv4 subnet of prefix length /30 or shorter, the total number of usable host addresses is calculated by the formula 2^(32 − prefix) − 2. The two subtracted addresses serve mandatory protocol functions defined in RFC 791 and RFC 919:

The RFC 3021 Exception (/31 Subnets): For modern point-to-point router-to-router serial or fiber links, RFC 3021 permits the use of /31 masks (2 total IPs). Because there are only two devices on the wire, there is no ambiguity: both addresses are assigned as usable endpoints with no need for separate broadcast or network IDs, saving millions of IP addresses across core telecom backbones.

In February 1996, the IETF published RFC 1918, designating three distinct blocks of IPv4 address space strictly for private, internal networks. Internet service providers and core Internet backbone routers are configured to immediately drop packets addressed to these destinations without routing them across the public Internet:

The Role of NAT / PAT: Because RFC 1918 addresses cannot traverse the public Internet, routers employ Network Address Translation (NAT) and Port Address Translation (PAT). When an internal computer connects to a public web server, the edge router replaces the private source IP (e.g. 192.168.1.45) with its single public WAN IP, tracking the session via an ephemeral source TCP port. This allows thousands of private devices to share a single routable public IPv4 address.

In the 2.4 GHz spectrum, each channel center is spaced only 5 MHz apart, but a standard Wi-Fi transmission occupies 20 MHz of spectral width. As a result, channels heavily bleed into neighboring frequencies: