Goldfish Networks wordmark
IntermediatePublished 2026-07-03

EIGRP Lab 6: Propagating a Default Route

Bundle lab

Inject a static default route from an edge router into an EIGRP domain so internal routers and hosts gain internet reachability. You will verify the D*EX 0.0.0.0/0 on the internal router and validate end-to-end connectivity from a branch host through the edge to an ISP-side server.

Track
Est. time
45 minutes
Difficulty
Intermediate
Topics

Learning objectives

  • Confirm an existing EIGRP adjacency and internal route exchange.
  • Originate a default route by redistributing a static 0.0.0.0/0 into EIGRP on the edge router.
  • Apply a valid EIGRP seed metric for redistribution on classic IOS.
  • Validate that the internal router installs a D*EX 0.0.0.0/0 and sets a gateway of last resort.
  • Prove end-to-end reachability from an internal host to an ISP-side server and interpret traceroute hops.

Troubleshooting focus

  • If R2 does not learn a default, check that R1 actually has a static 0.0.0.0/0 to the ISP next-hop and that EIGRP is redistributing static.
  • If redistribute static is present but no default appears, ensure a valid seed metric (or default-metric) is set for EIGRP external routes.
  • If there is no EIGRP neighbor, confirm matching AS (100), correct network statements for 10.0.12.0/30, and default K-values.
  • If the internal host can ping R2 but not the ISP, verify R2 shows a D*EX 0.0.0.0/0 via 10.0.12.1 and inspect the traceroute path.
  • If return traffic from the ISP-side server fails, ensure the ISP router has a static route back to 10.0.0.0/8 via 203.0.113.1.

Topology

Subscribe to preview this lab's topology.

See plans

Related labs

More hands-on Cisco Modeling Labs practice on the same track and topics.

Study this topic

Free guides, a command cheat sheet, and graded practice for this lab's topic.

Learn EIGRP

Grade your work

How this lab is graded
  • Build it your way. Where a lab lets you choose a value — a VLAN name, an interface description — grading checks that you configured it, not which name you picked. Names that another line has to reference, like an ACL applied with access-class, are stated in the guide and do have to match.
  • Addresses, modes and protocol keywords are exact. An IP address, a subnet mask, switchport mode trunk, an encapsulation — these carry the meaning of the lab, so they are graded as written in the guide.
  • Grading reads your saved configuration. Export the lab from CML after you have configured it, and make sure anything you set is in the running-config — a change that only exists in a terminal session never reaches the grader.
  • You can submit as many times as you like. Your best score stands, and each attempt tells you which checks passed so you can work the gaps.
  • Scored something you believe is correct? Use Report an issue on this page — that is exactly how the grading fixes in the changelog got found.

Create a free account to submit your lab for grading.

Create a free account
Found a problem with this lab?

Please sign in to report a problem — tying it to your attempts lets us reproduce and fix it faster.