The subnet mask is the least understood line in every network setting — and the simplest once you see it as a line drawn through the address. Street on one side, house number on the other.
Your PC makes one decision thousands of times a day: is this destination on my street or not? The subnet mask is the only thing it consults. Understand the mask and you understand why PCs on 'the same network' sometimes cannot see each other at all.
☝️ The mask is a stencil over the address. Where the mask says 255, that part is the street; where it says 0, that part is the house number.
The subnet mask does exactly one thing: it draws a line through the IP address. Everything on one side of the line is the street (the network), and everything on the other side is the house number (the device). Your PC uses this line for every single delivery decision.
The decision is brutally simple: if the street part matches mine, deliver directly; if it differs, send everything to the gateway. There is no third option, and the PC never phones a friend to ask.
With mask 255.255.255.0, each 255 means 'this part is street' and the 0 means 'this part is house'. So in 192.168.1.25 the street is 192.168.1 and houses run from .1 to .254.
Two addresses at the ends are reserved and are never given to a device: .0 names the street itself (the network address), and .255 is the broadcast address — a shout that every house on the street hears. That is the whole mystery behind '256 addresses but only 254 usable'.
Instead of writing the mask, people often write a slash: /24 = 255.255.255.0. The number counts how many street bits there are. More street bits means a smaller street:
Notice the pattern: usable devices is always the total minus 2, because of the network and broadcast addresses.
A wrong mask does not show an error — it just makes the PC draw the line in the wrong place. Set too wide, the PC tries to deliver directly to houses that are really on another street, and the data dies silently. Set too narrow, and the PC sends even next-door traffic to the gateway, which may refuse to send it back.
The classic symptom: some devices are reachable and some are not, on the same physical network. Before blaming cables, compare the mask on the failing PC with a working one — they must match.
The video walks through the mask with live addresses — once you watch the line being drawn, the /24 and /25 numbers stop being confusing.
▶️ Watch Full Video/24 is the short way of writing the mask 255.255.255.0. It means the first three numbers of the address form the network part. A /24 network has 256 addresses in total, and 254 of them can be assigned to devices.
Two addresses are reserved. The first, ending in .0, is the name of the network itself. The last, ending in .255, is the broadcast address used to talk to all devices at once. That leaves .1 to .254 — 254 addresses — for actual devices.
Sometimes, partly — which is what makes mask mistakes so confusing. If both PCs happen to see each other as 'same street', sharing works; otherwise traffic is pushed to the gateway and fails. The reliable fix is simple: every device on one network should carry the same mask.