IP Subnetting Made Simple: A Visual Guide

March 31, 2026 · 12 min read

What Is Subnetting?

Subnetting is the practice of dividing a larger network into smaller, more manageable pieces called subnets. Think of it like splitting a large office building into separate floors, each with its own reception desk and directory. Every floor (subnet) operates independently while still being part of the same building (network).

Why bother? Without subnetting, every device on a network shares the same broadcast domain. When one device sends a broadcast message, every other device has to process it. In a network with thousands of devices, this creates enormous amounts of unnecessary traffic.

Subnetting provides several critical benefits:

• Reduced broadcast traffic: Smaller broadcast domains mean fewer devices processing unnecessary messages
• Improved security: Network segments can be isolated with firewalls and access controls
• Better organization: Group devices logically by department, function, or location
• Efficient IP address allocation: Assign appropriately-sized address blocks to different segments
• Simplified troubleshooting: Isolate network issues to specific segments
• Enhanced performance: Reduce congestion by limiting broadcast domains

Consider a company with 500 employees. Without subnetting, all 500 devices would be on one flat network. Every ARP request, DHCP broadcast, and network announcement would reach every single device. With subnetting, you might create separate networks for Sales, Engineering, HR, and Guest WiFi—each isolated and manageable.

IP Addresses: The Basics

Before diving into subnetting, you need to understand IP addresses. An IPv4 address is a 32-bit number, typically written as four decimal numbers separated by dots—like 192.168.1.100. Each of those four numbers (called octets) ranges from 0 to 255, representing 8 bits.

In binary, that address looks like this:

192.168.1.100
= 11000000.10101000.00000001.01100100

Every IP address has two parts: the network portion (which identifies which network the device belongs to) and the host portion (which identifies the specific device on that network). The subnet mask determines where the boundary between these two parts falls.

IPv4 Address Classes (Historical Context)

Originally, IP addresses were divided into classes. While classful networking is largely obsolete, understanding these classes helps grasp subnetting fundamentals:

Today, we use Classless Inter-Domain Routing (CIDR), which allows flexible subnet sizing regardless of address class. This eliminates the waste inherent in classful networking.

Special IP Address Ranges

Certain IP ranges are reserved for specific purposes:

• 10.0.0.0/8: Private network (Class A)
• 172.16.0.0/12: Private network (Class B)
• 192.168.0.0/16: Private network (Class C)
• 127.0.0.0/8: Loopback addresses (localhost)
• 169.254.0.0/16: Link-local addresses (APIPA)
• 0.0.0.0/8: Current network
• 255.255.255.255: Broadcast address

Private addresses can be used freely within your network but cannot be routed on the public internet. This allows organizations to use the same private ranges internally without conflicts.

Subnet Masks Explained

A subnet mask looks like an IP address but serves a completely different purpose. It's a 32-bit pattern of consecutive 1-bits followed by consecutive 0-bits. The 1-bits mark the network portion, and the 0-bits mark the host portion.

For example, the subnet mask 255.255.255.0 in binary is:

11111111.11111111.11111111.00000000

This mask indicates that the first 24 bits represent the network, and the last 8 bits represent the host. When you perform a bitwise AND operation between an IP address and its subnet mask, you get the network address.

How Subnet Masks Work

Let's see this in action with IP address 192.168.1.100 and mask 255.255.255.0:

IP Address:    11000000.10101000.00000001.01100100 (192.168.1.100)
Subnet Mask:   11111111.11111111.11111111.00000000 (255.255.255.0)
               ---------------------------------------- (AND operation)
Network:       11000000.10101000.00000001.00000000 (192.168.1.0)

The result, 192.168.1.0, is the network address. All devices with IP addresses from 192.168.1.1 to 192.168.1.254 belong to this network.

Understanding Usable Hosts

Not all addresses in a subnet can be assigned to devices. Two addresses are always reserved:

• Network address: The first address (all host bits set to 0) identifies the network itself
• Broadcast address: The last address (all host bits set to 1) sends messages to all devices on the network

For a /24 network with 256 total addresses, you have 254 usable host addresses. The formula is: 2^{host bits} - 2

CIDR Notation

CIDR (Classless Inter-Domain Routing) notation provides a compact way to represent subnet masks. Instead of writing 255.255.255.0, you write /24—indicating that 24 bits are used for the network portion.

The notation format is: IP_address/prefix_length

Examples:

• 192.168.1.0/24 = subnet mask 255.255.255.0
• 10.0.0.0/8 = subnet mask 255.0.0.0
• 172.16.0.0/16 = subnet mask 255.255.0.0
• 192.168.1.128/25 = subnet mask 255.255.255.128

CIDR Conversion Table

Here's how CIDR prefixes map to subnet masks and host counts:

CIDR notation is now the standard in networking. It's more flexible than classful addressing and makes subnet calculations more intuitive once you understand the pattern.

Network and Host Portions

Understanding how IP addresses split into network and host portions is fundamental to subnetting. The subnet mask creates this division, and changing where that boundary falls is how we create subnets of different sizes.

Visualizing the Split

Consider the address 192.168.10.50/24:

IP Address:    192  .  168  .   10  .   50
Binary:        11000000.10101000.00001010.00110010
               |----Network (24 bits)---|--Host (8)--|
Subnet Mask:   11111111.11111111.11111111.00000000 (/24)

The first 24 bits (192.168.10) identify the network. The last 8 bits (50) identify the specific host on that network.

Borrowing Host Bits

When you subnet, you're "borrowing" bits from the host portion to create additional network bits. Each borrowed bit doubles the number of subnets but halves the number of hosts per subnet.

Starting with 192.168.10.0/24 (254 hosts), if we borrow 1 bit:

• New mask: /25 (255.255.255.128)
• Number of subnets: 2¹ = 2
• Hosts per subnet: 2⁷ - 2 = 126

The two resulting subnets are:

1. 192.168.10.0/25 (hosts: 192.168.10.1 - 192.168.10.126)
2. 192.168.10.128/25 (hosts: 192.168.10.129 - 192.168.10.254)

If we borrow 2 bits (creating a /26 mask):

• Number of subnets: 2² = 4
• Hosts per subnet: 2⁶ - 2 = 62

The four subnets become:

1. 192.168.10.0/26 (hosts: .1 - .62)
2. 192.168.10.64/26 (hosts: .65 - .126)
3. 192.168.10.128/26 (hosts: .129 - .190)
4. 192.168.10.192/26 (hosts: .193 - .254)

Calculating Subnets Step-by-Step

Let's walk through a complete subnetting problem from start to finish. This methodical approach works for any subnetting scenario.

Example Problem

You've been assigned the network 172.16.0.0/16 and need to create 30 subnets for different departments. What subnet mask should you use, and what are the first three subnet ranges?

Step 1: Determine Required Subnet Bits

How many bits do we need to borrow to create 30 subnets?

• 2⁴ = 16 subnets (not enough)
• 2⁵ = 32 subnets (sufficient)

We need to borrow 5 bits from the host portion.

Step 2: Calculate New Subnet Mask

Original mask: /16 (255.255.0.0)
Borrowed bits: 5
New mask: /21 (255.255.248.0)

In binary, the third octet becomes:

11111000 = 248

Step 3: Calculate Hosts Per Subnet

Remaining host bits: 32 - 21 = 11 bits
Hosts per subnet: 2¹¹ - 2 = 2046 usable hosts

Step 4: Find the Subnet Increment

Magic number: 256 - 248 = 8

Subnets increment by 8 in the third octet.

Step 5: List the Subnets

First three subnets:

1. 172.16.0.0/21
   • Network: 172.16.0.0
   • First host: 172.16.0.1
   • Last host: 172.16.7.254
   • Broadcast: 172.16.7.255
2. 172.16.8.0/21
   • Network: 172.16.8.0
   • First host: 172.16.8.1
   • Last host: 172.16.15.254
   • Broadcast: 172.16.15.255
3. 172.16.16.0/21
   • Network: 172.16.16.0
   • First host: 172.16.16.1
   • Last host: 172.16.23.254
   • Broadcast: 172.16.23.255

This pattern continues through all 32 subnets, incrementing by 8 in the third octet each time.

Common Subnets Reference Table

This comprehensive reference table shows the most commonly used subnet masks. Bookmark this page for quick reference when designing networks.

Note that /31 subnets are special—they're used for point-to-point links where the traditional network and broadcast addresses aren't needed, allowing both addresses to be used for hosts.

Real-World Subnetting Examples

Let's apply subnetting concepts to realistic scenarios you'll encounter in actual network design and administration.

Example 1: Small Business Network

Scenario: A company with 80 employees needs separate networks for Staff, Guest WiFi, Printers, and Servers.

Solution: Start with 192.168.0.0/24 and create four subnets using a /26 mask:

• Staff Network: 192.168.0.0/26 (62 hosts)
  • Range: 192.168.0.1 - 192.168.0.62
  • Use: Employee workstations and laptops
• Guest WiFi: 192.168.0.64/26 (62 hosts)
  • Range: 192.168.0.65 - 192.168.0.126
  • Use: Visitor devices, isolated from internal network
• Printers: 192.168.0.128/26 (62 hosts)
  • Range: 192.168.0.129 - 192.168.0.190
  • Use: Network printers and multifunction devices
• Servers: 192.168.0.192/26 (62 hosts)
  • Range: 192.168.0.193 - 192.168.0.254
  • Use: File servers, database servers, domain controllers

This design provides security isolation, easier troubleshooting, and room for growth in each segment.

Example 2: Multi-Site Enterprise

Scenario: A company with headquarters and three branch offices needs a scalable addressing scheme. HQ has 500 users, and branches have 100, 75, and 50 users respectively.

Solution: Use 10.0.0.0/8 private space with location-based addressing:

• Headquarters: 10.1.0.0/22 (1,022 hosts)
  • Provides room for growth beyond current 500 users
  • Can be further subnetted by department if needed
• Branch Office 1: 10.2.0.0/24 (254 hosts)
  • Accommodates 100 users with expansion capacity
• Branch Office 2: 10.3.0.0/25 (126 hosts)
  • Fits 75 users with some headroom
• Branch Office 3: 10.4.0.0/26 (62 hosts)
  • Suitable for 50 users with minimal waste

This hierarchical approach makes routing tables simpler and allows for easy addition of new sites using the 10.x.0.0 pattern.

Example 3: Data Center Segmentation

Scenario: A data center needs separate networks for web servers, application servers, database servers, and management interfaces.

Solution: Use 172.16.0.0/16 with security zones:

• DMZ (Web Servers): 172.16.10.0/24
  • Public-facing servers with restricted access
  • Firewall rules allow only HTTP/HTTPS inbound
• Application Tier: 172.16.20.0/24
  • Middle-tier application servers
  • Only accessible from DMZ and database tier
• Database Tier: 172.16.30.0/24
  • Backend databases with sensitive data
  • Most restrictive access controls
• Management Network: 172.16.100.0/24
  • Out-of-band management interfaces
  • Separate physical network for administration

This three-tier architecture with management separation is a security best practice for production environments.