Subnetting is one of those everyday networking tasks that looks simple until you need to plan multiple VLANs, check address boundaries, or fit several networks into a limited IP range.
A subnet calculator helps with the arithmetic. A good workflow should also help you understand the results and turn them into a usable addressing plan.
In this guide, we'll walk through practical IPv4 subnet calculations, CIDR notation, VLSM planning, and wildcard masks using Subnet CIDR Pro, an offline subnetting tool for iPhone and iPad.
Website: https://subnet.opshome.run/
App Store: https://apps.apple.com/us/app/subnet-cidr-pro/id6816397989
1. Calculate a subnet from an IP address
Let's start with a common example:
192.168.1.100/26
The /26 prefix means that 26 bits identify the network, leaving 6 bits for host addresses.
That gives us:
- Total addresses: 64
- Conventionally usable host addresses: 62
- Subnet mask:
255.255.255.192
Using Subnet CIDR Pro
- Open the subnet calculator.
- Enter
192.168.1.100and select the/26prefix. - Review the calculated network information.
- Copy the individual values you need or copy the complete summary.
The result should look like this:
| Field | Result |
|---|---|
| Network | 192.168.1.64/26 |
| Subnet mask | 255.255.255.192 |
| First usable address | 192.168.1.65 |
| Last usable address | 192.168.1.126 |
| Broadcast address | 192.168.1.127 |
| Wildcard mask | 0.0.0.63 |
| Usable hosts | 62 |
Notice that the entered address, 192.168.1.100, is a host address inside the subnet. It is not the network address itself.
This distinction matters when configuring VLAN interfaces, DHCP scopes, firewall rules, and static routes.
2. Understand what happens when the prefix changes
The prefix determines how much address space belongs to a subnet.
For example, compare /24, /26, and /28.
| Prefix | Total addresses | Conventional usable hosts |
|---|---|---|
/24 |
256 | 254 |
/26 |
64 | 62 |
/28 |
16 | 14 |
A /24 provides a larger address pool, while a /28 is better suited to a smaller network segment.
In Subnet CIDR Pro, adjust the prefix and review the updated network boundaries, mask, address range, and host capacity.
This is useful when deciding whether a subnet has enough room for the devices you expect to connect.
For example, a VLAN requiring 40 host addresses needs at least a /26 under conventional IPv4 subnetting rules. A /27 only provides 30 usable host addresses.
Don't choose a prefix based only on how many devices are connected today. Leave reasonable room for growth.
3. Plan multiple VLANs with VLSM
Calculating individual subnets is straightforward. Designing an entire addressing plan is more challenging.
Imagine a homelab or small office using the parent network:
10.20.0.0/24
You need separate networks for:
- Servers: 100 hosts
- Workstations: 50 hosts
- Management: 20 hosts
- Printers and other devices: 10 hosts
Allocating the same subnet size to every VLAN would waste address space.
This is where Variable Length Subnet Masking (VLSM) becomes useful.
A practical allocation
Start with the largest host requirement and work downward.
| Network | Required hosts | Allocation | Usable range |
|---|---|---|---|
| Servers | 100 | 10.20.0.0/25 |
.1–.126 |
| Workstations | 50 | 10.20.0.128/26 |
.129–.190 |
| Management | 20 | 10.20.0.192/27 |
.193–.222 |
| Printers | 10 | 10.20.0.224/28 |
.225–.238 |
The remaining block is 10.20.0.240/28, which can be reserved for future use.
How to use the VLSM planner
- Open the VLSM planning feature.
- Specify the parent network and the required host counts.
- Add meaningful labels for each network.
- Generate the allocation plan.
- Review the proposed prefixes and address boundaries before deploying them.
The important principle is to allocate the largest requirements first, then fit smaller networks into the remaining address space.
Always verify that every allocated subnet fits within the parent network and that no two allocations overlap.
A structured plan is easier to maintain than a collection of manually calculated addresses.
4. Convert subnet masks and wildcard masks
Subnet masks and wildcard masks are closely related, but they serve different purposes.
For example, a /26 subnet uses:
- Subnet mask:
255.255.255.192 - Wildcard mask:
0.0.0.63
A wildcard mask is the bitwise inverse of a subnet mask. It is commonly used in Cisco-style access control lists and routing configurations.
Instead of calculating each octet manually, use the mask converter to move between subnet masks, wildcard masks, and CIDR prefixes.
This is especially useful when translating an IP addressing plan into device configurations.
Remember that a wildcard mask is not interchangeable with a subnet mask in every command. Always check the syntax required by the target network device.
5. Use the CIDR reference for quick checks
Sometimes you don't need to calculate a complete subnet. You simply need to answer a question:
- How many addresses does
/27contain? - Which subnet mask corresponds to
/29? - What wildcard mask should I use for
/24? - How many usable hosts are available in a particular prefix?
The built-in CIDR reference lets you look up prefixes from /0 through /32 without repeatedly opening a separate browser-based calculator.
It's useful during troubleshooting, certification study, network planning, and configuration reviews.
6. Pay attention to special prefixes
Not every IPv4 subnet follows the conventional usable-host calculation.
Two important examples are /31 and /32.
/31 — Point-to-point links
RFC 3021 defines the use of /31 prefixes on IPv4 point-to-point links. Both addresses can be used as endpoint addresses in that context, without reserving a traditional network and broadcast address.
/32 — Single-host routes
A /32 identifies one IPv4 address. It is commonly used for host routes and other configurations that refer to a single address.
Subnet CIDR Pro handles these prefix boundaries explicitly, helping avoid incorrect assumptions when working with point-to-point links or single-host routes.
7. Why use an offline subnet calculator?
Network addressing information often appears in internal documentation, private infrastructure plans, and troubleshooting notes.
Subnet CIDR Pro performs its subnet calculations locally on the device. The calculation workflow does not require an account or a backend service, and results are copied only when you choose to copy them.
That makes it convenient when working in a lab, on-site, or in environments where connectivity is limited.
It also means you can calculate subnets without depending on an external website being available.
Final thoughts
Subnetting is not just about finding a network address. It is about making reliable decisions about address capacity, network boundaries, and future growth.
A practical workflow is simple:
- Calculate the subnet for an individual IP address.
- Adjust the prefix to evaluate address capacity.
- Use VLSM to plan multiple networks efficiently.
- Convert masks when working with routing or ACL configurations.
- Verify special prefixes before deploying the configuration.
Subnet CIDR Pro brings these IPv4 calculation and planning tasks into one focused iPhone and iPad workflow.
If you regularly work with VLANs, homelabs, routing, or small-office networks, having these calculations available offline can make address planning quicker and less error-prone.
Disclosure: Subnet CIDR Pro is my app. This article focuses on practical subnetting workflows rather than a complete feature review.
#devops #homelab #cidr
Top comments (0)