Get AI summaries of any video or article — Sign up free
let’s subnet your home network // You SUCK at subnetting // EP 6 thumbnail

let’s subnet your home network // You SUCK at subnetting // EP 6

NetworkChuck·
4 min read

Based on NetworkChuck's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Borrow host bits to create additional network bits; more subnets means more borrowed bits.

Briefing

A single home network can be made more secure by splitting it into multiple smaller subnets—specifically four networks—using subnetting rather than simply “adding networks” in a straightforward way. The practical payoff is isolation: wireless IoT devices, a DMZ, and user devices no longer share one flat address space, reducing the blast radius if something on one segment gets compromised.

The method starts with the existing subnet mask and the key idea that subnetting works by “stealing” bits from the host portion of the address space to create additional network identifiers. To get four networks, the process determines how many host bits must be converted into network bits. That bit count is derived through binary math: converting the required number of subnets into the smallest power-of-two that can cover it. For four networks, two bits are enough, meaning two host bits are flipped into network bits.

Once those bits are moved, the new subnet mask is rebuilt in binary and converted back to decimal. In the example, the resulting mask becomes 255.255.192.0, which corresponds to CIDR notation /26. That single change is the foundation for everything that follows: it defines both the size of each subnet and how addresses are allocated within them.

With /26 in hand, the next step is calculating the increment—the amount by which the network portion “jumps” from one subnet to the next. The increment equals the value of the last network bit in the subnet mask, which in this case is 64. That increment determines the address ranges for each of the four subnets. The first subnet starts at 192.168.0.0 and ends at 192.168.63.255 (broadcast at .63.255), the second runs 192.168.64.0–192.168.127.255, the third 192.168.128.0–192.168.191.255, and the fourth 192.168.192.0–192.168.255.255.

The episode then ties the subnet mask to host capacity. Because /26 leaves six host bits per subnet, each network contains 2^6 = 64 total addresses. Subtracting the subnet address and broadcast address leaves 62 usable host addresses per subnet. The episode emphasizes that this is not guesswork: the same counting logic applies whenever a subnet mask changes.

Finally, it frames the workflow as a reusable four-step approach: (1) decide how many subnets are needed, (2) determine how many bits to borrow, (3) compute the new subnet mask and CIDR, and (4) use the increment to list ranges and confirm host counts. The takeaway is that even if the address class feels different (Class B or Class A instead of Class C), the mechanics remain the same—only the numbers shift. A homework challenge asks viewers to redo the same network but split it into five subnets, reinforcing the idea that the bit-borrowing and increment logic scales to new requirements.

Cornell Notes

The core lesson is how to break one network into four smaller subnets securely by borrowing bits from the host portion of the subnet mask. For four networks, the smallest power-of-two that fits requires two borrowed bits, producing a new subnet mask of 255.255.192.0, or /26. With /26, the increment is 64, so the four subnet ranges progress in 64-block steps: .0–.63, .64–.127, .128–.191, and .192–.255. Each /26 subnet has 6 host bits, giving 2^6 = 64 total addresses and 62 usable host addresses after removing the subnet and broadcast addresses. This same workflow scales to other subnet counts by repeating the bit-borrowing and increment steps.

How does subnetting create more networks out of one existing network?

It converts part of the host field into the network field. When more subnets are needed, additional network bits must be created; the only way to do that is to “steal” bits from the host bits. Those borrowed bits change the subnet mask, which then defines both the size of each subnet and how addresses are grouped.

Why does four subnets require borrowing exactly two host bits?

Because the number of subnets must fit within a power of two. Four networks line up with 2^2, so two borrowed bits are sufficient. The episode also contrasts this with larger requirements (like 17 networks) where the next power of two (32) forces more borrowed bits than you might initially expect.

Given a /26 subnet mask (255.255.192.0), how do you find the increment and the subnet ranges?

The increment equals the value of the last network bit in the mask. For /26, that increment is 64. Starting from the base network, each subnet range advances by 64 in the relevant octet: 192.168.0.0–192.168.63.255, then 192.168.64.0–192.168.127.255, then 192.168.128.0–192.168.191.255, and finally 192.168.192.0–192.168.255.255.

How many usable host addresses exist in each /26 subnet?

A /26 mask leaves 6 host bits. That yields 2^6 = 64 total addresses per subnet. Subtract the subnet address and the broadcast address, leaving 62 usable host addresses.

What four-step workflow makes subnetting repeatable for different subnet counts?

(1) Determine how many subnets are required. (2) Convert that requirement into the number of bits to borrow (using the power-of-two logic). (3) Build the new subnet mask and express it in CIDR. (4) Use the increment to list address ranges and compute host capacity from the remaining host bits.

What changes when subnetting a Class B or Class A network instead of Class C?

The mechanics stay the same—borrow bits, compute the new mask, find the increment, and calculate host counts. What changes is the address layout and where the relevant octets fall, which can make the arithmetic feel different even though the underlying method is identical.

Review Questions

  1. If you need at least 17 subnets from an existing network, how do you determine how many host bits must be borrowed?
  2. For a /26 subnet, what is the increment and why does it determine the start and end of each subnet range?
  3. How do you compute usable host addresses from a subnet mask without memorizing values?

Key Points

  1. 1

    Borrow host bits to create additional network bits; more subnets means more borrowed bits.

  2. 2

    Use power-of-two logic to find the minimum number of bits needed for the required number of subnets.

  3. 3

    After building the new subnet mask, convert it to CIDR notation to keep calculations consistent.

  4. 4

    Compute the increment from the last network bit; the increment determines each subnet’s address range boundaries.

  5. 5

    For /26, the increment is 64 and each subnet spans 64 addresses in the relevant octet (e.g., .0–.63).

  6. 6

    Host capacity comes from remaining host bits: total addresses are 2^(host bits), and usable hosts equal total minus 2 (subnet + broadcast).

  7. 7

    A repeatable four-step process lets subnetting scale from four subnets to five, twelve, or more.

Highlights

Creating four subnets requires borrowing two host bits, turning the subnet mask into 255.255.192.0 (/26).
The increment for /26 is 64, which directly produces the four ranges: .0–.63, .64–.127, .128–.191, and .192–.255.
Each /26 subnet has 6 host bits, so it supports 62 usable host addresses (64 total minus subnet and broadcast).
Subnetting is framed as a consistent workflow: decide subnet count → borrow bits → compute mask/CIDR → use increment and host-bit math to list ranges.

Topics

  • Home Network Subnetting
  • CIDR /26
  • Subnet Mask Binary
  • Increment and Ranges
  • Host Address Counts

Mentioned

  • DMZ
  • CCNA
  • AWS
  • CIDR
  • IoT