Stackvora.tech

TCP/IP Subnetting: Master CIDR in 15 Minutes

Understanding TCP/IP subnetting is fundamental for efficient network design, security segmentation, and IP address management. Classless Inter-Domain…

Understanding TCP/IP subnetting is fundamental for efficient network design, security segmentation, and IP address management. Classless Inter-Domain Routing (CIDR), introduced in RFC 1519 and later updated by RFC 4632, replaced the older classful addressing scheme, offering greater flexibility and significantly mitigating IP address exhaustion. This guide demystifies CIDR, providing the practical knowledge needed to confidently subnet networks.

CIDR Fundamentals: Beyond Classful Addressing

Before CIDR, IP addresses were categorized into classes (A, B, C) with fixed network and host portions. Class A used the first 8 bits for the network, Class B the first 16, and Class C the first 24. This rigid structure led to inefficient address allocation. CIDR decouples the network mask from the IP address class, using a variable-length subnet mask (VLSM) denoted by a slash followed by a number (e.g., /24). This number represents the count of contiguous '1' bits from the left in the subnet mask, defining the network portion.

For example, 192.168.1.0/24 means the first 24 bits (11111111.11111111.11111111.00000000 in binary, or 255.255.255.0 in dotted decimal) are for the network address, leaving the remaining 8 bits for host addresses. This allows for much finer control over network sizing.

The Power of Two: Calculating Hosts and Subnets

The core of CIDR calculations relies on powers of two. The number of host bits (h) is calculated as 32 - CIDR_prefix. The number of available host addresses is 2h - 2. We subtract two because the all-zeros host address is reserved for the network address, and the all-ones host address is reserved for the broadcast address. The total number of addresses in a subnet is 2h.

Memorizing powers of 2 up to 1024 (or 210) is immensely helpful:

  • 20 = 1
  • 21 = 2
  • 22 = 4
  • 23 = 8
  • 24 = 16
  • 25 = 32
  • 26 = 64
  • 27 = 128
  • 28 = 256
  • 29 = 512
  • 210 = 1024

This directly translates to common CIDR blocks:

CIDR Prefix Subnet Mask (Dotted Decimal) Host Bits (h) Total Addresses (2h) Usable Hosts (2h - 2) Example
/32 255.255.255.255 0 1 1 (Loopback, host route) 10.0.0.1/32
/30 255.255.255.252 2 4 2 Point-to-point links
/29 255.255.255.248 3 8 6 Small office network
/28 255.255.255.240 4 16 14 Wireless AP subnet
/27 255.255.255.224 5 32 30 Medium department
/26 255.255.255.192 6 64 62 Large department
/25 255.255.255.128 7 128 126 Small campus segment
/24 255.255.255.0 8 256 254 Standard C-class equivalent
/23 255.255.254.0 9 512 510 Large campus network
/22 255.255.252.0 10 1024 1022 Data center rack

Practical Subnetting: Breaking Down a Network

Let's say you're given the network 172.16.0.0/20 and need to create several smaller subnets. A /20 means the first 20 bits are network, leaving 12 host bits (32-20=12). This network has 212 = 4096 total addresses (4094 usable hosts). The subnet mask is 255.255.240.0.

Scenario 1: Creating subnets for 100 hosts each

You need at least 100 usable hosts. Looking at our table, a /25 provides 126 usable hosts, and a /26 provides 62. So, /25 is the smallest prefix that satisfies the requirement.

A /25 network uses 25 network bits, leaving 7 host bits. From our initial /20, we've "borrowed" 5 bits (25-20=5) from the original host portion to create subnets. This means we can create 25 = 32 subnets.

Let's list the first few /25 subnets from 172.16.0.0/20:

  1. Subnet 1: 172.16.0.0/25
    • Network Address: 172.16.0.0
    • First Usable Host: 172.16.0.1
    • Last Usable Host: 172.16.0.126
    • Broadcast Address: 172.16.0.127
  2. Subnet 2: 172.16.0.128/25
    • Network Address: 172.16.0.128
    • First Usable Host: 172.16.0.129
    • Last Usable Host: 172.16.0.0.254
    • Broadcast Address: 172.16.0.255
  3. Subnet 3: 172.16.1.0/25 (The third octet increments after the second /25 block in the .0 octet)
    • Network Address: 172.16.1.0
    • First Usable Host: 172.16.1.1
    • Last Usable Host: 172.16.1.126
    • Broadcast Address: 172.16.1.127
  4. ...and so on, up to 172.16.15.128/25 (32 subnets in total within the /20 range).

The key here is understanding the block size. For a /25, the last octet (where the change happens for /25 through /31) increments by 2(32-25) = 27 = 128. For a /26, it would be 2(32-26) = 26 = 64. For /20, the block size in the third octet is 2(24-20) = 24 = 16, hence 172.16.0.0/20, 172.16.16.0/20, etc.

Supernetting: Route Aggregation with CIDR

Just as CIDR allows subnetting a large network into smaller ones, it also enables "supernetting" or route aggregation, where multiple smaller contiguous networks are combined into a single, larger CIDR block for routing purposes. This reduces the size of routing tables, improving router efficiency and convergence times.

Consider these four Class C equivalent networks:

  • 192.168.0.0/24
  • 192.168.1.0/24
  • 192.168.2.0/24
  • 192.168.3.0/24

To supernet these, we need to find the longest common prefix in their binary representations. The first two octets (192.168.) are common. Let's look at the third octet:

  • 0 = 00000000
  • 1 = 00000001
  • 2 = 00000010
  • 3 = 00000011

The common prefix for these four values is 000000 (the first six bits). Combined with the first two octets' 16 bits, this gives us 16 + 6 = 22 bits. So, these four /24 networks can be aggregated into a single 192.168.0.0/22 route. This is represented by the subnet mask 255.255.252.0.

Using Command-Line Tools for IP/Subnet Information

Operating systems provide tools to display and configure network interfaces, including their IP addresses and subnet masks. Understanding their output is crucial.

Linux/Unix

The ip addr show (or ip a) command is the modern standard, replacing the older ifconfig. 


$ ip a show eth0
2: eth0:  mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:11:22:33:44:55 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.100/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::211:22ff:fe33:4455/64 scope link 
       valid_lft forever preferred_lft forever

In this output, 192.168.1.100/24 clearly shows the IP address and its associated CIDR prefix. The brd 192.168.1.255 indicates the broadcast address derived from the /24 subnet mask.

Windows

The ipconfig /all command provides similar details. 


C:\Users\Admin>ipconfig /all

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : stackvora.tech
   Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
   Physical Address. . . . . . . . . : 00-1A-2B-3C-4D-5E
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.150(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, August 1, 2023 10:00:00 AM
   Lease Expires . . . . . . . . . . : Wednesday, August 2, 2023 10:00:00 AM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 192.168.1.1

Here, the "Subnet Mask" is explicitly shown in dotted-decimal format (255.255.255.0), which corresponds to a /24 CIDR prefix.

Trade-offs and Considerations in Subnetting

  • Broadcast Domain Size: Smaller subnets mean smaller broadcast domains, reducing network noise and improving performance. A large /16 network would have 65,534 usable hosts, all receiving each other's broadcasts, which is generally undesirable.
  • Security: Subnetting allows for network segmentation, enabling firewalls and ACLs to control traffic flow between different logical segments (e.g., separating user networks from server farms, or different departments).
  • IP Address Utilization: Aggressive subnetting (e.g., using /30 for point-to-point links) conserves IP addresses. Conversely, using a /24 for only 5 hosts wastes 249 addresses. Balancing host requirements with address conservation is key.
  • Routing Complexity: While supernetting reduces routing table size, excessive or poorly planned subnetting can complicate routing protocols, especially if routes are not properly aggregated.
  • VLSM Implementation: Variable Length Subnet Masks (VLSM) are critical. You might have a /24 for an office, /27 for a specific server VLAN, and /30 for router-to-router links, all within a larger allocated block.

Common Pitfalls

  • Incorrect Broadcast/Network Address Calculation: A common mistake is assigning the network address or broadcast address to a host. Always remember these are reserved.
  • Overlapping Subnets: Accidentally creating subnets with overlapping IP address ranges. This leads to unpredictable network behavior and routing issues. Always verify your subnet ranges.
  • Miscalculating Host Requirements: Not accounting for growth or specific device needs (e.g., network printers, management interfaces, VoIP phones) when determining subnet size, leading to premature re-subnetting.
  • Forgetting Default Gateway: Every device on a subnet needs a default gateway configured to communicate outside its local subnet. This is typically the router interface's IP address within that subnet.
  • Binary Conversion Errors: Manual binary-to-decimal conversions can be error-prone. Double-check your work or use reliable online calculators for verification until you're proficient.

Back to the knowledge base · Ask the AI assistant