Before you can read the parent note, you must own every piece of notation it throws at you. This page builds each one from absolute zero, in an order where each idea leans only on the ones before it.
The picture: imagine a light switch. Down = 0, up = 1. That is a bit.
Why the topic needs it: a network address must be stored inside a computer, and computers physically hold information as huge rows of these off/on switches. So the "address" is literally a pattern of switches.
Once you have several switches in a row, you need a rule that turns a pattern of switches into an ordinary number. That rule is positional notation, and it is exactly how our normal decimal numbers work — we just swap 10 for 2.
What it looks like: each switch that is on drops its column-value onto a pile; switches that are off drop nothing. The size of the pile is your number.
Everything about powers of two here is developed further in Binary and Positional Number Systems.
The picture: take 8 switches from §1 and draw a box around them. That box is one octet.
Why the topic needs it:32 raw switches in a row are unreadable to a human. We chop the row into four octet-boxes and write each box as a single decimal number 0–255. That packaging is the "dotted-decimal" address.
So 192.168.0.1 is really the 32-switch row
11000000 . 10101000 . 00000000 . 00000001,
just written in friendlier chunks. The dots are pure decoration for human eyes — the machine only ever sees 32 switches in a line.
Why the topic needs it: every address you will ever type or subnet is in this form. The whole game of the parent note is deciding how to split these 32 switches.
The picture: the 32 switches with a single amber divider bar. Slide the bar right → more street switches, fewer house switches → smaller streets, more of them.
Why the topic needs it: classes, subnetting, and CIDR are only three different rules for choosing where this one line goes. Get this picture and the rest is bookkeeping.
Now that the line of §6 exists, here are the three named rules the parent note uses, each with a tiny example so the words are not just labels.
Why the topic needs it:/n is just a compact name for where §6's line sits. Bigger n = line further right = fewer house switches = smaller network. (Keep this: bigger n means smaller network — the parent note's Trap 2.)
The list below is a top-down dependency map: read it downward, and each indented item means "you need the thing above it before the thing below makes sense." (A machine-readable Mermaid version is tucked inside the collapsible box after it, for readers whose viewer renders diagrams.)
bit (§1) — the on/off switch
positional value 2i (§2) — turns switches into a number
octet, max 255 (§3)
dotted decimal a.b.c.d (§4)
network vs host line (§6) — also needs2n below
/n prefix + mask (§7–8)
hosts =2h−2 (§9) — also needs2n below
PARENT: classes, subnetting, CIDR
2n counts patterns (§5) — feeds the network/host line, the host formula, and:
232 total addresses
The parent topic (parent topic) sits at the very bottom: it assumes all of §1–§9. This page built them.
Recall Mermaid version of the same map (only shows if your viewer renders diagrams)
h=32−n and 2h−2 → parent §4 and every host-count example
Once every checklist line is automatic, you are equipped for the full IPv4 topic, and downstream for IPv6 — addressing and notation and Routing Tables and Longest Prefix Match.