Subnetting…..but in reverse

A host losing all network access can come down to a simple but non-obvious subnetting mistake: the IP address might be “valid” for its subnet, yet the default gateway can land in a different subnet entirely—leaving the machine unable to ping anything, including the internet. The core task is “reverse subnetting,” where subnetting has already been applied and the job becomes reconstructing the network, broadcast, and valid host ranges from an existing IP configuration.

The walkthrough starts with real-world-style troubleshooting. Using an IP address, subnet mask, and default gateway from a problem host (Beatrice), the goal is to determine the network address, broadcast address, and network range. Because the subnet mask is already present, the process focuses on working backward: convert the subnet mask from decimal to binary, identify the slash length by counting contiguous “1” bits, then compute the increment (the value of the last network bit). That increment dictates where network boundaries fall.

With the mask converted to binary, the subnet is determined to be /20, meaning the increment is 16. Instead of incrementing in the usual fourth octet (common with class C thinking), the boundaries shift in the third octet. That’s the key mental pivot: network ranges advance by 16 in the third octet, producing ranges like 172.17.0.0–172.31.0.255 (with the network address and broadcast address derived accordingly). The example also highlights a subtle validity check: an IP ending in 255 can be a broadcast address and normally shouldn’t be assigned—but depending on the size of the subnet, even values that look suspicious at first glance can still fall within a valid range. In this case, Beatrice’s IP is treated as valid for its subnet.

Even with a valid IP, connectivity still fails. The reason emerges when comparing subnets between hosts. Bernard Hackwell’s IP places him in a different network segment than Beatrice—effectively “on different planets.” The decisive clue is Beatrice’s default gateway: it points to 172.17.0.1, which is not in the same subnet as her actual network. Since routers only forward traffic when the destination is outside the local subnet—and because the gateway itself isn’t reachable as a local neighbor—Beatrice can’t even reach the router, so pings to Bernard and external destinations fail.

By reconstructing the subnet boundaries from the configured mask, the troubleshooting becomes mechanical: compute the network address, broadcast address, and range; verify whether the default gateway belongs to the same subnet; then confirm whether other hosts share that same network range. The episode frames reverse subnetting as a practical superpower for CCNA-style exam questions and real troubleshooting tickets, ending with a teaser: the next step is subnetting a subnet—pushing the same logic further into more complex scenarios.