One octet = eight bits
A bit is either 0 (off) or 1 (on). Each position doubles as you move left: 1, 2, 4 … 128.
0100101074= sum of the switched-on weightsSTACKIT ACCESS DOMAIN · SECOND STAGE
A visual crash lab for subnetting, VPNs, cloud networking, Kubernetes, and Go—built for explaining your reasoning out loud.
01 / ADDRESSING
Turn ambiguous address questions into four precise facts: network, broadcast, usable range, and capacity.
Do not memorise CIDR as a magic trick. First see the address as 32 switches; then CIDR simply draws a line between the network switches and the host switches.
A bit is either 0 (off) or 1 (on). Each position doubles as you move left: 1, 2, 4 … 128.
0100101074= sum of the switched-on weights000010100001100000001000010001102 network bits · 6 host bitsThe prefix is counted from the left. /26 means 24 full bits from the first three octets, plus 2 more bits from the last octet. The remaining 6 bits identify a host inside that subnet.
10.24.8.70/26 on a number line./26 means the final octet begins 11000000, which is 128 + 64 = 192. Mask: 255.255.255.192.
In the interesting octet: 256 − 192 = 64. So the possible subnet blocks begin at 0, 64, 128, 192.
70 sits in 64–127. Therefore the network is .64 and broadcast is .127.
Six host bits give 2⁶ = 64 total addresses. Remove network and broadcast: 62 usable, .65–.126.
“Prefix is the fence; host bits are the houses.” Count host bits for capacity. Use the mask’s interesting octet for block size. Then locate the address between the block boundaries.
How many hosts must this subnet support?
usable hosts = 2host bits − 2Network + broadcast are reserved*“/26 leaves 6 host bits, so it has 64 total addresses / 62 usable. Its mask is 255.255.255.192; blocks increment by 64 in the final octet.”
02 / PROTOCOL MAPS
HTTP, DNS and TLS give applications a shared language. In an interview, distinguish protocol responsibility from the physical network beneath it.
HTTP · DNS · TLS03 / THE MODERN WEB
04 / CLOUD REASONING
Connect Kubernetes concepts to operational outcomes: discoverability, routing, desired state and safe convergence.
Interview lens: a Service gives a stable virtual IP; the CNI provides Pod reachability; kube-proxy (or eBPF replacement) steers Service traffic to endpoints.
net/netip in one minute05 / PRACTICE OUT LOUD
Commit to an answer, then use the feedback as your speaking structure.
06 / LAST 10 MINUTES
/24 = 256 addresses
Hosts = 232 − prefix − 2/26 → 62 usable
SNAT changes source for egress.
DNAT changes destination for ingress.
PAT also changes ports.
IPsec protects IP traffic.
IKEv2 negotiates SAs/keys.
ESP commonly provides encryption.
Pod IPs are ephemeral.
Services are stable virtual IPs.
Operators reconcile desired state.
QUIC over UDP.
Streams avoid TCP connection-level head-of-line blocking.
Fast connection setup.
netip gives typed, immutable IP values.
Prefer netip.Addr / Prefix for new code.