Subnet Calculator Guide: CIDR, Subnetting, and IP Address Planning for Network Engineers

You're designing a network for a 200-employee company. They need separate subnets for departments, guest access, and IoT devices. Your boss wants the IP scheme documented by Friday. Sound familiar?

IP address planning separates competent network engineers from those who wing it and regret it later. This guide covers practical subnetting, CIDR notation, and the calculations that matter when you're actually building networks.

Understanding CIDR Notation and Subnet Masks

CIDR (Classless Inter-Domain Routing) notation tells you exactly how many bits define the network portion of an IP address. The number after the slash indicates network bits.

192.168.1.0/24 means:

• First 24 bits define the network (192.168.1)
• Last 8 bits define hosts (0–255)
• Subnet mask: 255.255.255.0

192.168.0.0/16 means:

• First 16 bits define the network (192.168)
• Last 16 bits define hosts (0.0 to 255.255)
• Subnet mask: 255.255.0.0

The subnet mask determines which portion of the IP address identifies the network versus individual hosts. Each bit set to 1 in the mask represents the network portion.

Common CIDR Blocks and Their Capacities

| CIDR | Subnet Mask | Available Hosts | Typical Use | |------|-------------|-----------------|-------------| | /30 | 255.255.255.252 | 2 | Point-to-point links | | /29 | 255.255.255.248 | 6 | Small server clusters | | /28 | 255.255.255.240 | 14 | Department networks | | /27 | 255.255.255.224 | 30 | Branch offices | | /26 | 255.255.255.192 | 62 | Medium departments | | /25 | 255.255.255.128 | 126 | Large departments | | /24 | 255.255.255.0 | 254 | Standard LAN segment |

Remember: Available hosts = 2^(32-CIDR) - 2. You lose two addresses for network and broadcast.

Calculating Network Addresses and Broadcast Addresses

Every subnet has a network address (first IP) and broadcast address (last IP). These aren't assignable to hosts.

Network Address Calculation

Take any IP in a subnet and apply the subnet mask using bitwise AND.

Example: 192.168.50.75/26

Convert to binary:

IP:        11000000.10101000.00110010.01001011
Mask (/26):11111111.11111111.11111111.11000000

Apply AND operation:

Result:    11000000.10101000.00110010.01000000
Network:   192.168.50.64

Broadcast Address Calculation

Set all host bits to 1.

Continuing the example:

Network:    192.168.50.64/26
Host bits:  last 6 bits
Broadcast:  192.168.50.127

Usable range: 192.168.50.65 to 192.168.50.126 (62 hosts)

Variable Length Subnet Masking (VLSM)

VLSM lets you create subnets of different sizes from a single network block. This prevents IP waste and matches subnet size to actual requirements.

VLSM Planning Process

1. List requirements by size (largest first)
2. Assign subnets starting with the largest
3. Use remaining space for smaller subnets

Example: Subnetting 192.168.100.0/24

Requirements:

• Sales: 50 hosts
• Engineering: 30 hosts
• HR: 10 hosts
• Management: 5 hosts
• Point-to-point links: 2 each

Allocation:

Sales:       192.168.100.0/26   (62 hosts available)
Engineering: 192.168.100.64/27  (30 hosts available)
HR:          192.168.100.96/28  (14 hosts available)
Management:  192.168.100.112/29 (6 hosts available)
P2P Link 1:  192.168.100.120/30 (2 hosts available)
P2P Link 2:  192.168.100.124/30 (2 hosts available)

This leaves 192.168.100.128/25 (128 addresses) for future growth.

Subnet Design for Different Network Types

Enterprise Campus Networks

Three-tier approach:

• Core: /30 links between core routers
• Distribution: /29 for distribution-access links
• Access: /24 or /25 for user subnets

Example enterprise scheme:

10.0.0.0/16 - Campus network
├── 10.0.1.0/24  - Building A users
├── 10.0.2.0/24  - Building B users
├── 10.0.10.0/24 - Servers
├── 10.0.20.0/24 - Guest network
└── 10.0.254.0/24 - Management

Data Center Networks

Leaf-spine architecture:

• Loopbacks: /32 (single addresses)
• Spine-leaf links: /31 (RFC 3021)
• Server subnets: /25 or /26

Branch Office Networks

Typical branch allocation:

192.168.X.0/24 per branch
├── 192.168.X.0/26  - Users (62 hosts)
├── 192.168.X.64/28 - Servers (14 hosts)
├── 192.168.X.80/28 - Printers/IoT (14 hosts)
└── 192.168.X.96/27 - Guest (30 hosts)

IPv6 Subnetting Fundamentals

IPv6 uses /64 as the standard subnet size. The 128-bit address space makes different planning considerations necessary.

Standard IPv6 allocation:

• /48 — Site allocation
• /56 — Small site or large customer
• /64 — Single subnet (standard)

Example IPv6 scheme:

2001:db8:1000::/48 - Organization
├── 2001:db8:1000:1::/64  - Building 1
├── 2001:db8:1000:2::/64  - Building 2
└── 2001:db8:1000:10::/64 - Servers

IPv6's massive address space eliminates the conservation mindset required for IPv4. Focus on hierarchy and summarization instead of efficiency.

Common Subnetting Mistakes to Avoid

Overlapping Subnets

Wrong:

192.168.1.0/24
192.168.1.128/25  ← overlaps with first subnet

Correct:

192.168.1.0/25    (192.168.1.0–127)
192.168.1.128/25  (192.168.1.128–255)

Insufficient Growth Planning

Don't size subnets exactly to current needs. Plan for 2–3x growth minimum. A department with 20 users needs /26 (62 hosts), not /27 (30 hosts).

Ignoring Summarization

Design subnets so you can summarize routes efficiently. Keep related subnets numerically adjacent.

Good for summarization:

10.1.16.0/24
10.1.17.0/24
10.1.18.0/24
10.1.19.0/24

Summarizes to: 10.1.16.0/22

Mixing Public and Private Incorrectly

Never use public IP ranges for internal networks. Stick to RFC 1918:

• 10.0.0.0/8
• 172.16.0.0/12
• 192.168.0.0/16

Practical Subnet Calculator Usage

When you're doing real network planning, manual calculation gets tedious fast. You need tools that handle the math while you focus on design decisions.

A good subnet calculator should:

• Show network, broadcast, and usable ranges instantly
• Support VLSM planning across multiple subnets
• Validate that your scheme doesn't overlap
• Export results in formats you can actually use

The key is finding tools that give you answers, not just raw calculations. You want to spend time on network design, not binary math.

Network Documentation and IP Address Management

Document your IP scheme before implementation. Include:

• Network/CIDR
• Purpose/Department
• VLAN ID
• Gateway IP
• DHCP range
• Static reservations

Example documentation:

Network:  10.50.10.0/24
Purpose:  Engineering Department
VLAN:     110
Gateway:  10.50.10.1
DHCP:     10.50.10.100–200
Static:   10.50.10.10–50 (servers)

Keep this updated. Undocumented networks become problem networks.

Advanced Subnetting Scenarios

Merging Networks After Acquisition

You inherit 192.168.1.0/24 but already use 192.168.0.0/16. Solutions:

• Renumber the acquired network
• Use NAT at the boundary
• Implement route summarization

Multi-Site WAN Design

Connect sites efficiently:

• Use /30 for point-to-point WAN links
• Reserve /29 blocks for future circuits
• Plan for MPLS, internet backup, and direct connections

Cloud Integration Planning

Reserve address space for:

• VPN connections to AWS/Azure/GCP
• Hybrid cloud subnets
• Container orchestration (Kubernetes needs large blocks)

Modern networks span on-premises and cloud. Plan accordingly.

Conclusion

Effective IP address planning requires understanding CIDR notation, calculating network boundaries accurately, and designing for growth and summarization. The math matters, but the real skill is creating schemes that scale and make operational sense.

Whether you're subnetting a single /24 for a branch office or designing address space for a multi-site enterprise, the principles remain consistent: plan for growth, avoid overlaps, document everything, and choose tools that give you answers instead of homework.

Ready to put these concepts into practice? Try the Subnet Calculator on CyrusX.