Chapter 12: Binary and Subnet Masks
This chapter follows the topics shown in the Networking chapter menu. Work through each section in order, then use the review questions to check recall and troubleshooting reasoning.
12.1 Decimal vs Binary
Decimal vs Binary is one of the core topics in Binary and Subnet Masks. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Decimal vs Binary in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.2 Binary Bits
Binary Bits is one of the core topics in Binary and Subnet Masks. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Binary Bits in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.3 Powers of Two
Powers of Two is one of the core topics in Binary and Subnet Masks. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Powers of Two in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.4 Converting Decimal to Binary
Converting Decimal to Binary is one of the core topics in Binary and Subnet Masks. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Converting Decimal to Binary in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.5 Converting Binary to Decimal
Converting Binary to Decimal is one of the core topics in Binary and Subnet Masks. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Converting Binary to Decimal in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.6 IPv4 Octets
IPv4 Octets is one of the core topics in Binary and Subnet Masks. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place IPv4 Octets in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.7 Subnet Mask Binary
An IPv4 subnet mask identifies which address bits belong to the network prefix and which bits are available for host addressing.
Example: place Subnet Mask Binary in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.8 CIDR Prefix Length
CIDR writes the prefix length after a slash, such as /24. The prefix length is the number of leading address bits treated as the network portion.
Example: place CIDR Prefix Length in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.9 /8
A /8 IPv4 prefix uses 8 network bits and 24 host bits. Its equivalent subnet mask is 255.0.0.0; one subnet contains 16,777,216 total addresses and conventionally 16,777,214 host addresses when network and broadcast addresses are reserved.
Example: if a network is documented as 192.0.2.0/8, the prefix length tells the router which leading bits identify the subnet. The mask is 255.0.0.0; the subnet size is 16,777,216 addresses. Use binary boundaries, not visual guessing, to find the next subnet.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.10 /16
A /16 IPv4 prefix uses 16 network bits and 16 host bits. Its equivalent subnet mask is 255.255.0.0; one subnet contains 65,536 total addresses and conventionally 65,534 host addresses when network and broadcast addresses are reserved.
Example: if a network is documented as 192.0.2.0/16, the prefix length tells the router which leading bits identify the subnet. The mask is 255.255.0.0; the subnet size is 65,536 addresses. Use binary boundaries, not visual guessing, to find the next subnet.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.11 /24
A /24 IPv4 prefix uses 24 network bits and 8 host bits. Its equivalent subnet mask is 255.255.255.0; one subnet contains 256 total addresses and conventionally 254 host addresses when network and broadcast addresses are reserved.
Example: if a network is documented as 192.0.2.0/24, the prefix length tells the router which leading bits identify the subnet. The mask is 255.255.255.0; the subnet size is 256 addresses. Use binary boundaries, not visual guessing, to find the next subnet.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.12 /25
A /25 IPv4 prefix uses 25 network bits and 7 host bits. Its equivalent subnet mask is 255.255.255.128; one subnet contains 128 total addresses and conventionally 126 host addresses when network and broadcast addresses are reserved.
Example: if a network is documented as 192.0.2.0/25, the prefix length tells the router which leading bits identify the subnet. The mask is 255.255.255.128; the subnet size is 128 addresses. Use binary boundaries, not visual guessing, to find the next subnet.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.13 /26
A /26 IPv4 prefix uses 26 network bits and 6 host bits. Its equivalent subnet mask is 255.255.255.192; one subnet contains 64 total addresses and conventionally 62 host addresses when network and broadcast addresses are reserved.
Example: if a network is documented as 192.0.2.0/26, the prefix length tells the router which leading bits identify the subnet. The mask is 255.255.255.192; the subnet size is 64 addresses. Use binary boundaries, not visual guessing, to find the next subnet.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.14 /27
A /27 IPv4 prefix uses 27 network bits and 5 host bits. Its equivalent subnet mask is 255.255.255.224; one subnet contains 32 total addresses and conventionally 30 host addresses when network and broadcast addresses are reserved.
Example: if a network is documented as 192.0.2.0/27, the prefix length tells the router which leading bits identify the subnet. The mask is 255.255.255.224; the subnet size is 32 addresses. Use binary boundaries, not visual guessing, to find the next subnet.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.15 /28
A /28 IPv4 prefix uses 28 network bits and 4 host bits. Its equivalent subnet mask is 255.255.255.240; one subnet contains 16 total addresses and conventionally 14 host addresses when network and broadcast addresses are reserved.
Example: if a network is documented as 192.0.2.0/28, the prefix length tells the router which leading bits identify the subnet. The mask is 255.255.255.240; the subnet size is 16 addresses. Use binary boundaries, not visual guessing, to find the next subnet.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.16 /29
A /29 IPv4 prefix uses 29 network bits and 3 host bits. Its equivalent subnet mask is 255.255.255.248; one subnet contains 8 total addresses and conventionally 6 host addresses when network and broadcast addresses are reserved.
Example: if a network is documented as 192.0.2.0/29, the prefix length tells the router which leading bits identify the subnet. The mask is 255.255.255.248; the subnet size is 8 addresses. Use binary boundaries, not visual guessing, to find the next subnet.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.17 /30
A /30 IPv4 prefix uses 30 network bits and 2 host bits. Its equivalent subnet mask is 255.255.255.252; one subnet contains 4 total addresses and conventionally 2 host addresses when network and broadcast addresses are reserved.
Example: if a network is documented as 192.0.2.0/30, the prefix length tells the router which leading bits identify the subnet. The mask is 255.255.255.252; the subnet size is 4 addresses. Use binary boundaries, not visual guessing, to find the next subnet.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.18 Block Size
Block Size is one of the core topics in Binary and Subnet Masks. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Block Size in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.19 Network Boundaries
Network Boundaries is one of the core topics in Binary and Subnet Masks. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Network Boundaries in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
12.20 Host Capacity
Host Capacity is one of the core topics in Binary and Subnet Masks. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Host Capacity in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.