Every networking course eventually hits the same wall: subnetting. The concept isn't actually hard — it's the notation that trips people up. Once you see it as "splitting one big neighborhood into smaller streets," it clicks.

What a subnet actually is

An IP network is a block of addresses. Subnetting takes that block and divides it into smaller blocks, each one able to operate as its own segment — its own broadcast domain, with its own routing boundary. This matters for real reasons: smaller subnets reduce broadcast traffic, isolate departments or floors from each other, and make troubleshooting far easier because a problem stays contained to one segment.

CIDR notation, without the fear

You'll see addresses written like 192.168.1.0/24. That /24 is the CIDR prefix — it tells you how many bits, from the left, are "fixed" as the network portion. The remaining bits are free for host addresses.

A /24 leaves 8 bits for hosts (32 total bits − 24 network bits), which gives 256 addresses in that block, with 254 usable after reserving the network and broadcast address.

The rule that unlocks everything: every time you borrow one more bit for the network portion (/24 → /25 → /26...), you cut the number of addresses in that block in half, and double the number of subnets you can create from the original range.

A worked example

Say you're given 192.168.10.0/24 and asked to create 4 equal subnets for four office departments. You need enough new bits to represent 4 groups, and 2 bits gives you exactly 4 (2² = 4). So you move from /24 to /26.

Each block has 64 addresses, 62 of them usable once you set aside the network and broadcast address at each end.

The habit that makes it stick

Don't memorize a chart — practice converting the last octet to binary a few times by hand until you can see, instinctively, how many bits a given prefix leaves free. Once that becomes automatic, the exam questions (and the real-world VLAN planning) stop being scary and start being arithmetic.

Written by Elisha Manchare