Static routes are typically used in small, simple networks where:
There are no redundant paths.
The network topology doesn't change often.
As networks grow in size and complexity, managing static routes becomes difficult and error-prone. In such cases, dynamic routing protocols (like OSPF or EIGRP) are a better fit, as they automatically adjust to network changes and provide path redundancy.
Consider the following network setup:
Router A has a directly connected network: 1.1.1.0
Router C has a directly connected network: 3.3.3.0
Now, imagine a host on the 1.1.1.0 network (connected to Router A) needs to send a packet to a host on the 3.3.3.0 network (connected to Router C). By default, Router A only knows how to reach its directly connected network (1.1.1.0). Without additional routing information, it will drop any packets destined for 3.3.3.0
To enable communication between these networks, you need to manually configure static routes on each router:
Router A: Add a static route to the 3.3.3.0 network using Router B as the next hop.
Router B: Add a static route to the 3.3.3.0 network using Router C as the next hop.
To ensure return traffic can reach its source, static routes must also be configured in the opposite direction:
Router C: Add a static route to the 1.1.1.0 network using Router B as the next hop.
Router B: Add a static route to the 1.1.1.0 network using Router A as the next hop.
Once these static routes are in place, here's how traffic will flow:
A host on 1.1.1.0 sends a packet to a host on 3.3.3.0.
Router A forwards the packet to Router B.
Router B forwards it to Router C.
Router C delivers the packet to the 3.3.3.0 network.
For return traffic:
Router C sends the packet back to Router B.
Router B forwards it to Router A.
Router A delivers it to the original host on 1.1.1.0.