Static & Default Routing

Configure a default route on a branch edge router and a return static route on an upstream core router to enable full bidirectional connectivity between a stub branch LAN and a core server LAN. Verify the S* default route, gateway of last resort, and end-to-end reachability from real hosts. Troubleshoot missing default or return paths.

Hands-on CCNA static routing and manual summarization lab using a compact HQ–Branch–Remote topology. You will replace three specific static routes to Branch networks with a single /22 summary at HQ, verify end-to-end host reachability, observe the routing table reduction, and prevent over-aggregation loops by adding a Null0 discard route at Branch. A recommended step has you add the same /22 summary at Remote (replacing its default) to practice summarization on both sides.

Deploy primary static routes between two branch LANs via a hub router and add a higher-AD floating static for a direct inter-branch backup. Verify end-to-end reachability, simulate a hub outage to trigger automatic failover, then restore the primary path. Includes realistic addressing, unique /30 transits, and host-based verification.

Build a small HQ–WAN–Branch triangle with two independent WAN paths. Configure equal-cost static routes on both edge routers so traffic to the opposite site’s LAN installs with two next-hops and is load-shared by CEF. Verify end-to-end reachability from real hosts, observe per-flow load sharing on the routers, and compare behavior to a floating static of higher administrative distance.

Hands-on IPv6 static and default routing across a 3-router, 2-LAN topology with end-user hosts. You will enable IPv6 unicast routing, apply IPv6 addressing, configure hub-and-spoke static and default routes, and validate bidirectional host reachability. The guide provides scenario context, step-by-step tasks with the why behind each action, and targeted troubleshooting.

Deploy a compact two-site topology with a WAN core and two end hosts to practice IPv4 static host routes (/32) versus subnet routes (/24). You will configure a specific /32 host route to steer one destination host over the direct R1–R3 path while a broader /24 for the same remote LAN is sent via the R1–R2–R3 core. Validate with show commands and traceroute, then troubleshoot longest-prefix match and return-path issues.

Design and implement a 3-router full-mesh with two edge LANs using static IPv4 routes only. Edges use primary defaults toward the core plus floating (higher AD) backup defaults; the core uses specific routes for the edge LANs. Validate bidirectional reachability, path choice, and failover behaviors from real hosts.

Build a 3-router triangle with two branch LANs and real Alpine clients. Deploy primary static routes via the hub and floating backup statics over a direct branch-to-branch link. Verify reachability, path selection, and failover by simulating a hub outage.

Hands-on CCNA static routing troubleshooting in a realistic three-router core/edge topology with two user LANs. Static routing on the network was recently changed and users at SITE-A (10.10.10.10) and SITE-B (10.30.30.10) can no longer reach each other; you will investigate the routers' route tables and next-hop reachability to diagnose and restore full bidirectional connectivity.