Ridge Station Seven Depot 7 loses its uplink connecting 47:12
authenticating

Lab 19 — Configure IPv4 static and default routes

CCNA — NorthRidge Station · Module 4: Routing concepts · Estimated 45 minutes

OBJECTIVES

  • Configure a directly connected static route using an exit interface.
  • Configure a recursive static route using a next-hop IP address.
  • Configure a fully specified static route.
  • Configure a default static route.
  • Verify connectivity and interpret the output of show ip route.

BACKGROUND

A router forwards a packet only if its destination matches an entry in the routing table. Without configuration, that table contains only directly connected networks — the ones its own interfaces sit on. Every other destination is unreachable and the packet is dropped.

A static route is an entry you place in the table by hand. It does not adapt, it does not advertise itself, and it does not disappear when a distant link fails. That is both its weakness and, in a small or stub topology, its virtue: the table says exactly what you put in it.

COMMAND SYNTAX

Router(config)# ip route network-address subnet-mask { next-hop-ip | exit-interface }
FormWritten asLookups
Directly connectedip route 10.0.111.0 255.255.255.0 s0/1/1one
Recursiveip route 10.0.111.0 255.255.255.0 10.0.255.6two
Fully specifiedip route 10.0.111.0 255.255.255.0 s0/1/1 10.0.255.6one
Defaultip route 0.0.0.0 0.0.0.0 10.0.255.1varies
WHY THE FORM MATTERS

A recursive route names an IP the router must look up a second time to learn where to send the frame. On a point-to-point serial link the exit interface form avoids that lookup. On a multi-access link such as Ethernet, the exit-interface-only form is not recommended — the router cannot know which of many neighbours to address, so use the fully specified form instead.

ADDRESSING TABLE

DeviceInterfaceAddressMask
R1G0/0/010.0.100.1255.255.255.0
R1S0/1/010.0.255.1255.255.255.252
R2S0/1/010.0.255.2255.255.255.252
R2S0/1/110.0.255.5255.255.255.252
R2G0/0/010.0.107.1255.255.255.0
R3S0/1/110.0.255.6255.255.255.252
R3G0/0/010.0.111.1255.255.255.0
PC-ANIC10.0.100.10255.255.255.0
PC-CNIC10.0.111.10255.255.255.0

PART 1 — VERIFY THE STARTING STATE

  1. On R1, issue show ip route. Record how many routes are present and what code each carries.

    You should see only C and L entries. C is the connected network; L is the /32 local address of the interface itself.

  2. From R1, ping 10.0.255.2. It should succeed — it is on a directly connected network.
  3. From R1, ping 10.0.111.1. It will fail. Issue show ip route 10.0.111.1 and confirm the router reports % Network not in table.

PART 2 — CONFIGURE STATIC ROUTES ON R1

  1. Configure a directly connected static route to the Depot 7 LAN:
    R1(config)# ip route 10.0.107.0 255.255.255.0 s0/1/0
  2. Configure a recursive static route to the Depot 11 LAN:
    R1(config)# ip route 10.0.111.0 255.255.255.0 10.0.255.2
  3. Issue show ip route static. Both entries appear with code S. Note the administrative distance and metric in brackets — [1/0] — and be able to say what each number means.
  4. Ping 10.0.111.1 again. It will still fail.

    Do not configure anything else on R1. Work out why before reading Part 3 — the answer is the single most common static routing mistake.

PART 3 — THE RETURN PATH

R1 now knows how to reach Depot 11. R3 does not know how to reach anything beyond its own two networks, so the echo reply has nowhere to go. A route is one-directional; reachability is not.

  1. On R3, configure a default static route pointing back toward R2:
    R3(config)# ip route 0.0.0.0 0.0.0.0 10.0.255.5

    R3 is a stub — it has exactly one way out, so a default route is correct here and enumerating individual networks would be noise.

  2. On R2, add routes to the two LANs it does not own.
  3. Re-test. The ping should now succeed in both directions.

VERIFICATION

CommandWhat it answers
show ip routethe whole table, with codes
show ip route staticonly what you configured
show ip route 10.0.111.10which entry would be used, and why
show ip interface briefwhether a link is the problem
traceroute 10.0.111.10where the path actually stops

REFLECTION

  1. Why does a static route configured on one router not produce two-way reachability?
  2. The default route in Part 3 is written 0.0.0.0 0.0.0.0. Explain, in terms of the longest-match rule, why this never prevents a more specific route from being used.
  3. Both static routes on R1 showed [1/0]. What would you change to make one of them a floating static route, and when is that useful?

Topology

Lab 19 · three routers, two serial links, two host LANs

R1 HQ R2 Depot 7 R3 Depot 11 S0/1/0 S0/1/0 S0/1/1 S0/1/1 G0/0/0 G0/0/0 G0/0/0 10.0.255.0/30 10.0.255.4/30 S1 S3 PC-A 10.0.100.10 PC-C 10.0.111.10 10.0.100.0/24 10.0.107.0/24 10.0.111.0/24 Depot 7 LAN Serial links are point-to-point. No routing protocol is configured on any device.

INTERFACE SUMMARY

RouterSerial 0/1/0Serial 0/1/1Gig 0/0/0
R110.0.255.110.0.100.1
R210.0.255.210.0.255.510.0.107.1
R310.0.255.610.0.111.1
READ THE TOPOLOGY BEFORE THE TABLE

R1 and R3 each touch exactly one serial link, which makes them stubs. R2 touches both, which makes it the only device that needs to know about networks on either side. Deciding that from the diagram, before typing, is most of the work in this lab.