LogoفارسیFA

Hands-On Lab: Configuring Static Routing via Interfaces

This hands-on lab configures static routes using an outgoing interface rather than a next-hop IP address, demonstrating this approach's suitability for point-to-point links and its important limitation on multi-access networks.

Static Route Interface SyntaxPoint-to-Point RoutingRecursive Lookup

~3 min read · Updated Sep 22, 2026

Lab Objective

Configure static routes on two routers using the outgoing interface syntax rather than specifying a next-hop IP address, and verify traffic routes correctly across a point-to-point serial link.

Lab Purpose

Static routes, discussed earlier in this series, can be configured pointing to either a next-hop IP address or an outgoing interface. The interface-based syntax works cleanly on point-to-point links but should generally be avoided on multi-access networks, a distinction this lab makes concrete.

Lab Topology

R1 ---- Serial0/0/0 ------ Serial0/0/0 ---- R2

R1: 10.20.20.1/30, LAN 192.168.10.0/24 (Loopback1)
R2: 10.20.20.2/30, LAN 192.168.20.0/24 (Loopback1)

Task 1: Configure Basic Addressing

Configure the serial interfaces and a loopback on each router representing its local LAN.

Task 2: Configure a Static Route Using the Outgoing Interface on R1

On R1, configure a static route to R2's LAN using R1's serial interface as the outgoing interface, rather than a next-hop address.

Task 3: Configure the Equivalent Route on R2

On R2, configure a static route to R1's LAN using the same interface-based syntax.

Task 4: Verify Connectivity

Confirm R1 can reach R2's LAN and vice versa.

Task 5: Examine the Routing Table Entry

Note how the route appears differently in the routing table compared to a next-hop-based static route.

Solution and Verification

R1(config)# interface serial0/0/0
R1(config-if)# ip address 10.20.20.1 255.255.255.252
R1(config-if)# no shutdown
R1(config-if)# exit
R1(config)# interface loopback1
R1(config-if)# ip address 192.168.10.1 255.255.255.0

R2(config)# interface serial0/0/0
R2(config-if)# ip address 10.20.20.2 255.255.255.252
R2(config-if)# clock rate 64000
R2(config-if)# no shutdown
R2(config-if)# exit
R2(config)# interface loopback1
R2(config-if)# ip address 192.168.20.1 255.255.255.0

R1(config)# ip route 192.168.20.0 255.255.255.0 serial0/0/0

-- The outgoing interface (serial0/0/0) is
-- specified instead of R2's serial IP address

R2(config)# ip route 192.168.10.0 255.255.255.0 serial0/0/0

R1# ping 192.168.20.1

!!!!!
Success rate is 100 percent (5/5)

R1# show ip route static

S    192.168.20.0/24 is directly connected, Serial0/0/0
-- Notice the route is listed as "directly
-- connected" rather than "via" a next-hop
-- address -- this is a distinguishing
-- characteristic of interface-based static
-- routes, since the router treats the entire
-- destination network as reachable directly
-- out that interface

Key Takeaway

Interface-based static routes work well on true point-to-point links like this serial connection, since there is only one possible destination for anything sent out that interface. On a multi-access network like Ethernet, however, this same syntax forces the router to ARP for every destination address individually rather than just the next hop, creating unnecessary overhead — next-hop-based static routes are generally preferred except on genuinely point-to-point media.

Written & researched by Dr. Shahin Siami

Related Articles

Hands-On Lab: Configuring IPv6 Static Routes

This hands-on lab configures static routes for IPv6 destinations between two routers, mirroring the IPv4 static routing syntax covered earlier in this series while highlighting the IPv6-specific command keyword and address format.

Continue

Hands-On Lab: Configuring Default Static Routes

This hands-on lab configures a default static route on an edge router to reach the internet through an ISP connection, demonstrating how a single route can represent every otherwise-unknown destination rather than requiring individual routes for each one.

Continue

Hands-On Lab: Configuring and Naming Static Routes

This hands-on lab configures static routes with descriptive names attached using the name keyword, improving documentation and making the routing table significantly easier to interpret for anyone reviewing the configuration later.

Continue

Hands-On Lab: Configuring Static Routing via IP Addresses

This hands-on lab configures static routes using a next-hop IP address rather than an outgoing interface, the generally preferred syntax, and compares the resulting routing table entry against the interface-based approach from the previous lab.

Continue

Hands-On Lab: Installing a Wireless LAN Controller

This hands-on lab performs the initial setup of a Wireless LAN Controller, joins a lightweight access point to it, and creates a centrally managed WLAN, demonstrating the controller-based architecture that scales far beyond standalone access points.

Continue

Hands-On Lab: Installing a Wireless Access Point

This hands-on lab covers physically connecting and performing the initial configuration of a standalone wireless access point, including setting up an SSID, applying WPA3 security, and verifying wireless clients can associate and reach the wired network.

Continue
Previous ArticleNext Article