Directly connected routes only allow a router to see networks physically wired to its own chassis. The moment an organization establishes a remote branch office in another city, connected across a dedicated WAN link, the local routers are blind to the remote office subnets. Unless you teach the router where that remote network lives, communication between offices is completely impossible.
The simplest, most reliable way to bridge two locations is through Static Routing. By manually entering an explicit route statement into each router, you define the exact path packets must follow. In this chapter, you will connect a Headquarters network to a Branch Office network, configure bidirectional static routes, and verify cross-office reachability.
The Golden Law of Bidirectional Routing
The number one mistake made by new network technicians is configuring a static route in only one direction. They log into the Headquarters router, configure a route telling it how to reach the Branch Office, and assume the job is done. When they attempt to ping across the link, the ping fails 100% of the time.
Remember this fundamental rule: Routing must always be bidirectional. An ICMP ping consists of two packets: an Echo Request going forward, and an Echo Reply coming back. If the Headquarters router knows how to reach the Branch, but the Branch router does not know how to return packets to Headquarters, the request arrives at the remote PC, but the reply is dropped immediately by the remote router!
| Router Device | Target Remote Network | Subnet Mask | Next-Hop Gateway IP | Exit Interface |
|---|---|---|---|---|
| HQ Router | 192.168.20.0 | 255.255.255.0 (/24) | 10.0.0.2 | GigabitEthernet0/1 |
| Branch Router | 192.168.10.0 | 255.255.255.0 (/24) | 10.0.0.1 | GigabitEthernet0/1 |
The Anatomy of the ip route Command
On industry standard network equipment, static routes are created in global configuration mode using the ip route command. The command requires three distinct arguments:
Router(config)# ip route [Destination-Network] [Subnet-Mask] [Next-Hop-IP]On the Headquarters router, we execute: ip route 192.168.20.0 255.255.255.0 10.0.0.2. This instructs the router: Whenever you receive a packet destined for the Branch subnet (192.168.20.0/24), forward it across the WAN link to the neighboring router IP address 10.0.0.2.
On the Branch router, we configure the exact mirror return path: ip route 192.168.10.0 255.255.255.0 10.0.0.1. This completes the communication circle, ensuring that both outbound requests and inbound replies find their way home without interruption.
Next-Hop IP versus Outgoing Exit Interface
When writing static routes, administrators have the choice of specifying the Next-Hop IP address, the Outgoing Exit Interface, or both simultaneously. While pointing to an exit interface like GigabitEthernet0/1 works seamlessly on point-to-point serial links, using next-hop IP addresses is the recommended best practice for multi-access Ethernet connections.
If you specify only an exit interface on an Ethernet link, the router treats the destination network as if it were directly connected to that broadcast segment. Consequently, the router attempts to send ARP requests for every single individual remote host IP address, bloating ARP tables and generating unnecessary broadcast noise. Using next-hop IP addresses avoids this problem entirely.
When a next-hop IP is specified, the router performs a quick recursive lookup to determine which local interface reaches that next hop, and then addresses Layer 2 Ethernet frames directly to the MAC address of the neighboring gateway router.
Recursive Lookups in Routing Tables
A recursive lookup occurs when the router must resolve the next-hop IP address against another entry in the routing table. For instance, when a packet arrives destined for 192.168.20.0/24, the router checks its table and discovers the next hop is 10.0.0.2. It then performs a secondary lookup for 10.0.0.2, discovering it is reachable directly out of interface GigabitEthernet0/1.
Modern routers cache these lookup results using specialized hardware forwarding engines. This ensures that static routes configured with next-hop IP addresses perform line-rate packet forwarding without causing high CPU utilization.
Verifying Static Routes with show ip route
Once you enter the commands, execute show ip route on both routers to inspect the results. The new entry appears prefixed with the code S (Static), accompanied by bracketed values indicating the Administrative Distance and Metric: [1/0].
An Administrative Distance of 1 means the router trusts this static route more than any dynamic routing protocol (such as OSPF with distance 110). Static routes represent explicit administrator intent, so they take precedence over automated route advertisements.
Hands-On Lab Practice
In this lab exercise, you will connect Headquarters PC (192.168.10.10) to Branch PC (192.168.20.10) across two routers linked by a 10.0.0.0/30 WAN segment. You will configure the static routes on both routers, verify routing table entries, and achieve 100% successful bidirectional ping communication.
Watch for the TTL decrement during the ping test. Because the packet crosses two routers (HQ Router and Branch Router), the TTL counter decrements twice, arriving with TTL=62. This provides concrete mathematical proof of two-hop routing.