WHY SUBNETTING FINALLY
CLICKED FOR ME

I spent three weeks genuinely confused about subnetting. Not "I need to review this a bit more" confused. Actually, staring-at-the-ceiling-at-midnight confused. I'd read the explanations. I'd watched the videos. I could recite the process mechanically and still get answers wrong under any kind of time pressure.

Then something clicked. Not from a new resource — from a different starting point inside the same material I'd already read a dozen times. If subnetting isn't landing for you either, this is what I wish someone had told me in week one.

★ WHY MOST GUIDES START FROM THE WRONG END

Almost every subnetting guide starts with binary. "Convert the IP to binary, AND it with the subnet mask, and you get the network address." That's correct — and if it clicks for you immediately, build on it. Binary is the right foundation.

My problem wasn't the binary explanation. It was that I jumped straight to speed techniques before I actually understood what subnetting is. The binary made sense in isolation but I couldn't connect it to a fast answer under exam pressure. What I needed first was a mental model for the concept itself — then the binary and the shortcuts both fell into place on top of it.

Here's the mental model that finally worked for me:

Once that landed, the binary made sense. The math made sense. I wasn't converting numbers to figure something out — I was confirming where the boundaries I already understood in my head actually fell.

★ THE FRAMEWORK THAT ACTUALLY WORKS

Here's how I think through any subnetting question now. No binary required for most of it.

STEP 1: KNOW YOUR POWERS OF 2

Need /8 through /32 with subnet masks, wildcard masks, and block sizes? Full CIDR cheat sheet →

These numbers are powers of 2 — each step down adds one host bit. The "borrows bits" framing is useful but needs context: when people say a /25 "borrows 1 bit from a /24, giving 2 subnets of 128," they mean relative to a /24 parent block. If your parent block is a /22 the math changes. The cheat sheet above gives you absolute address counts per prefix — use those as your starting point, then apply them to whatever address space you're actually working inside.

STEP 2: FIND THE BLOCK SIZE

The block size is the magic number. It's just 256 minus the last non-255 octet of the subnet mask.

The block size tells you where your subnets start and end within the interesting octet. For masks in the last octet (/25 through /30) subnets always start at multiples of the block size in that octet. This shortcut works cleanly there. For masks like /20, /21, /18, /23 where the interesting octet shifts left, the same principle applies but you need to identify which octet is actually changing — the last fully-masked octet isn't always the fourth. Get comfortable with last-octet masks first, then extend the same logic leftward.

STEP 3: LIST YOUR SUBNET BOUNDARIES

Given 192.168.10.0/27, the block size is 32. So your subnets start at:

You don't calculate each one separately. You count up by block size: 0, 32, 64, 96, 128, 160, 192, 224. The network address is always the first, broadcast is always one less than the next network address, usable hosts are everything in between.

WHY THIS MATTERS UNDER EXAM PRESSURE

Here's a real exam-style question: which subnet does 192.168.10.100 belong to? What's the network address, broadcast, and usable range?

If you know /27 = block of 32, you immediately count up your boundaries: 0, 32, 64, 96, 128. The address 100 falls between 96 and 128 — so the answer is:

That's the gap the block size approach closes. You might fully understand the binary — 27 network bits, 5 host bits, 2⁵ = 32 addresses — and still freeze on where 100 actually lands when the clock is running. Counting multiples of 32 in your head is fast. Binary AND operations under pressure are not.

★ THE VLSM PROBLEM — AND WHY IT'S EASIER THAN IT LOOKS

Variable Length Subnet Masking (VLSM) sounds intimidating. It's just subnetting a subnet — allocating different sized blocks from the same address space based on actual requirements. The same rules apply, you're just doing it in layers.

The key is always to start with the largest requirement and work down. Allocate the biggest subnet first, then carve out smaller ones from the remaining space. Never allocate a larger block from space that's already been used.

★ A NOTE ON ORDER — BINARY FIRST IS STILL RIGHT

After posting about this, someone made a good point: the ideal path is probably binary foundation first, speed techniques second. Learn why /27 means 27 network bits and 5 host bits. Understand that each octet shares the same bit value order — 128, 64, 32, 16, 8, 4, 2, 1. See how /27 sits exactly 3 hops right of /24 and lands on the 32 bit slot, which is also your block size. That pattern repeats across every octet boundary.

Once that relationship between binary and block size clicks, the cheat sheet stops being memorization and starts being something you could derive yourself. That's a much stronger position to be in on exam day.

My mistake was jumping to the shortcuts before the foundation was solid. If you're early in your CCNA prep, do it in the right order — Jeremy's IT Lab covers the binary side better than anything else I've found. Then come back to the block size approach as a speed layer on top of real understanding.

★ WHAT ACTUALLY MADE IT STICK

Reading helped. Videos helped. But what actually made subnetting automatic was repetition under time pressure.

I used subnettingpractice.com every single day for two weeks. Not to study — just to drill. Set a timer, answer questions, check results, repeat. After about 200 reps the mental model stopped being something I recalled and started being something I just did.

This is the same principle behind Ironman training. You don't think about your stroke when you're swimming at kilometre 3 of the swim leg. You've done it enough times that your body just knows. Subnetting works the same way. The goal isn't to understand it — it's to internalize it until understanding isn't even the right word anymore._