Static Routing lab practice
Read the routing table, add static and default routes in both directions, and prove reachability with ping and traceroute.
7 labs · 11 lessons · 6 commands · 5 projects
A router forwards each packet by finding the longest matching prefix in its routing table. Connected networks appear automatically; anything else has to be learned, either from a routing protocol or from a static route you configure.
Static routing is where routing troubleshooting is learned: every path needs a route there and a route back, a default route handles everything else, and ping and traceroute show where a path breaks.
Hands-on labs
- IP Static Routing Setup (Pro)
- Gateway of Last Resort (Pro)
- Several Static Routes on One Router (Pro)
- Default Route on an Edge Router (Pro)
- Specific Routes Alongside a Default (Pro)
- Adding the Missing Return Route (Pro)
- Gateway Unreachable: a Mistyped Interface Address (Pro)
To practise for free, build the topology in the free Sandbox.
Lessons, in order
- Routing Fundamentals (3. IP Connectivity, 9 min)
- Static & Default Routes (3. IP Connectivity, 8 min)
- Life of a Packet (3. IP Connectivity, 15 min)
- Read the routing table and add a default route (3. IP Connectivity, 12 min)
- Add static routes in both directions (3. IP Connectivity, 13 min)
- Extend static routing across a transit router (3. IP Connectivity, 13 min)
- Troubleshoot a failed ping by checking forward and return paths (3. IP Connectivity, 12 min)
- Break an IPv4 static routing loop (3. IP Connectivity, 12 min)
- Add a floating static backup route (3. IP Connectivity, 13 min)
- Assessment: Default Route (3. IP Connectivity, 10 min)
- Two decisions: install the route, then forward the packet (3. IP Connectivity, 11 min)
Commands
- show ip route — Shows the IPv4 routing table: every network the router can reach, how it learned it, and the next hop or exit interface.
- show ip route static — Shows only the static routes that are installed in the routing table.
- ping — Sends ICMP echo requests to an address and reports how many replies came back and the round-trip times.
- traceroute — Lists each router hop on the path to a destination, so you can see where forwarding stops.
- show ip interface brief — Lists every interface with its IPv4 address and its Layer 1 and Layer 2 status in one line each.
- show ip arp — Shows the router’s ARP cache: which MAC address it has resolved for each IPv4 address, and on which interface.
Related projects
- Headquarters and Branch Static Routing — Marlow Joinery's head office and its new workshop across town are joined by a leased line. Neither site can see the other's LAN. Route between them by hand, in both directions.
- Two-Router Branch Link with Symmetric Static Routes — A surveying firm has an office and a yard a mile apart, joined by a leased line. Each site has its own LAN and neither can see the other. Build the routing in both directions.
- Haulage Firm Hub-and-Spoke Static Routing — A haulage firm has a head office and two depots, each with its own router and LAN, connected head office to depot over two metro Ethernet circuits. The routers are cabled and nothing is configured; the depots cannot reach the dispatch server at head office or each other. Address the routers from the plan, give each depot a single default route to head office, give head office a route to each depot LAN, and prove depot-to-depot traffic crosses the head office router.
- Two-Site Branch WAN with Point-to-Point Serial & Static Routing — A regional manufacturer operates a corporate Headquarters and an automated Warehouse facility 40 miles away. The sites are interconnected across a dedicated leased serial link. You must configure HDLC encapsulation, clock rate timing on the DCE boundary, and bidirectional static routes to interconnect both LANs.
- Dual-Circuit Branch: Floating Static Failover with a Pinned Probe Route — A small branch has a fibre circuit and a cheaper DSL backup from the same provider. The provider routes the branch's /29 (203.0.113.8/29) to the fibre, and to the DSL only when the fibre is gone. Today BR-RTR has no default route at all. Make the fibre primary and the DSL a floating backup, pin the route to the provider's resolver so a health probe can only ever measure the fibre, prove the failover, and design the IP SLA and tracking that would also catch a fibre circuit that is up but not passing traffic.