Learn how static routes specify forwarding choices, how routers use them, and how route availability and administrative distance affect routing decisions.
What you will be able to do
- Define a static route and explain how it identifies a destination and next hop.
- Describe how a router uses a packet’s destination address and routing table to select a next hop.
- Explain when a static route is removed because its forwarding path is no longer valid.
- Contrast static routes with dynamic routes using administrative distance.
01
What a Static Route Is
A static route is a route that a user creates to guide packets toward a destination through a chosen path. It gives the router an explicit forwarding instruction rather than leaving that choice entirely to learned routing information.
The destination can be represented by a network prefix, such as the address range that identifies a group of reachable networks. The route also identifies a next-hop router, which is the device expected to receive the packet next.
02
Why Static Routes Are Useful
Static routing is useful when an administrator wants a particular destination to follow a deliberately selected path. The route makes that forwarding choice visible in the router’s configuration.
For example, a router could be configured to send traffic for the prefix 10.20.0.0/16 to a neighboring router at 192.0.2.9. The prefix identifies the destination group, while the next-hop address identifies the immediate forwarding device.
03
How the Router Selects a Next Hop
For an ordinary IP unicast packet, the router generally consults its routing table to determine where the packet should go next. The table provides forwarding information associated with possible destinations.
The lookup begins with the packet’s IP Destination Address. If the address belongs to a configured destination prefix, the router can use that route’s next-hop information for forwarding.
04
From Destination to Neighbor
Consider a packet whose destination address falls within 10.20.0.0/16. If the routing table contains the example static route, the router selects 192.0.2.9 as the next hop instead of treating the destination address as the immediate neighbor.
This distinction matters because the destination and the next hop serve different roles. The destination describes where the packet ultimately belongs, while the next hop describes the next router along the selected path.
05
When a Static Route Is Removed
A static route depends on a usable forwarding path. When the interface used by that route goes down, the route is removed from the IP routing table.
A route can also disappear when its configured forwarding device no longer has a valid next hop. In both cases, the configured instruction cannot currently lead traffic through a valid forwarding device.
06
Static and Dynamic Routes
A static route is entered by a user, while a dynamic route is learned through routing information exchanged by devices. These are different ways for a router to obtain possible paths.
Administrative distance expresses how trustworthy routing information is considered from a device or device group. A dynamic route can replace a static route when the static route has a higher administrative distance.
07
Why Administrative Distance Matters
Administrative distances need careful, consistent assignment when several routing sources can describe paths. Poor choices can contribute to routing loops or other network failures.
Therefore, a static route is not automatically preferred simply because it was configured manually. Its relationship with other routes depends partly on the administrative distance assigned to the competing information.
08
A Special Case: Interface-Based Routes
A static route that points to an interface can be treated as connected. When that happens, it no longer keeps its static character in the routing system.
Routes treated as connected can be advertised by routing protocols. This behavior differs from the usual expectation that a manually created route remains only a local forwarding instruction.
09
Maintenance Considerations
A router that supports dynamic routing must allow static routes to use metrics that are valid for its routing protocols. This keeps the static route compatible with the router’s routing behavior.
Avoid clearing routing tables without a clear reason. An unnecessary flush can remove the default route and particular routes to network sites, changing how traffic is forwarded.
10
Recap: Ready for Practice and Prove
A static route is a user-defined forwarding instruction. It associates a destination prefix with a selected next-hop router.
For an ordinary IP unicast packet, the router generally consults its routing table to determine where the packet should go next. The table provides forwarding information associated with possible destinations.
Consider a packet whose destination address falls within 10.20.0.0/16. If the routing table contains the example static route, the router selects 192.0.2.9 as the next hop instead of treating the destination address as the immediate neighbor.
A static route depends on a usable forwarding path. When the interface used by that route goes down, the route is removed from the IP routing table.