Field note / IPv4 troubleshooting

The gateway must be reachable before it can help.

For a destination outside its connected subnet, a host needs a usable route. A default route is useful only if its next hop can be reached.

Work the branch example

The workstation is 10.10.10.10/24. Its connected subnet spans 10.10.10.0 to 10.10.10.255. The router's branch interface, 10.10.10.1/24, is on that segment. The portal, 10.20.20.80, is outside it.

A default gateway of 10.10.10.254 passes the subnet-membership test, but this network has no interface at that address. Membership is necessary here; it does not establish that a neighbor exists. Set the gateway to the router's actual interface, 10.10.10.1.

A larger subnet can make the wrong decision

Change only the client prefix to /8. Both 10.10.10.10 and 10.20.20.80 now fall in the client's calculated 10.0.0.0/8 subnet. The workstation treats the portal as on-link instead of forwarding through the gateway. In this topology the server is on a different Ethernet segment, so local delivery cannot reach it. A broader mask did not create a physical connection.

Follow the reply too

After the forward path works, remove the server return route in the exercise. The router can deliver the request, but the server cannot send its reply to the client. A one-way path does not establish a working exchange.

Route-selection background: RFC 1812, section 5.2.4. Prefix notation: RFC 4632, section 3.1. The fixed topology and observations above are Patchbay Lab's original worked example.

Repair the branch network