Lab 5: Static Routing Between Two Routers
Two offices, two routers, one serial/ethernet link — make LAN-A reach LAN-B with static routes configured in both directions (the classic beginner miss: forgetting the return route). Difficulty: Intermediate · Time: ~30 min.
Lab objectives
- Address two LANs and the router-to-router link
- Write a static route on each router for the remote LAN
- Understand why BOTH directions are needed
- Verify end-to-end ping
Topology & addressing
R1: LAN 192.168.1.0/24 (Gi0/0 = .1), link Gi0/1 = 10.0.0.1/30. R2: LAN 192.168.2.0/24 (Gi0/0 = .1), link Gi0/1 = 10.0.0.2/30. One PC in each LAN with its router as gateway.
Step-by-step configuration
R1: ip route 192.168.2.0 255.255.255.0 10.0.0.2 | "To reach LAN-B, send via R2" |
R2: ip route 192.168.1.0 255.255.255.0 10.0.0.1 | The return route — without it pings die on the way back |
Verification
show ip route on each router — an S entry for the remote LAN. PC-A → PC-B ping succeeds only when both routes exist. Remove R2's route and watch pings fail — requests arrive, replies can't return. That lesson sticks forever.
Done? Try the next lab on the labs hub, or test your knowledge on the free CCNA practice test. Get Packet Tracer free via the career hub.
Frequently asked questions
Why do I need routes on both routers?
Routing is per-direction: R1's route delivers the request, but R2 needs its own route to send replies back. One-way routing means failed pings.
What does the S mean in show ip route?
A static route configured manually by an administrator.
When would I use a default route instead?
When all unknown traffic should go one way (e.g. to the internet): ip route 0.0.0.0 0.0.0.0
Related articles
Want hands-on training?
Learn this on real Cisco lab devices with placement support at Attila Technologies, Ahmedabad.