EIGRP Stub Routing on a Spoke (Hub-and-Spoke, AS 100)

Bundle lab · $29.99

Configure a classic hub-and-spoke EIGRP domain where the single-homed branch (R2) is made an EIGRP stub, limiting query scope while still advertising its LAN. Validate that R1 flags R2 as a stub neighbor, routes still exchange, and query behavior is scoped appropriately.

Learning objectives

• Build a hub-and-spoke EIGRP domain using a single AS (100) and classless operation (no auto-summary).
• Configure R2 (single-homed spoke) as an EIGRP stub advertising only connected routes.
• Ensure LAN-facing interfaces are passive so EIGRP never forms adjacencies toward hosts.
• Verify the stub flag from the hub (R1) and confirm normal route advertisement continues.
• Compare behavior with and without a stub to understand how query scope is reduced.

Troubleshooting focus

• Confirm all routers use the same EIGRP AS (100) and default K-values.
• Check that each transit subnet is enabled under EIGRP with the correct wildcard mask.
• Ensure host-facing interfaces are passive; only router-to-router transits should form neighbors.
• Verify that R2 is actually in stub mode (eigrp stub connected) and that R1 recognizes it as a stub neighbor.
• If a route is missing, confirm it is connected and matched by a network statement on the originating router.