IPv6 static routes look almost identical to IPv4 static routes. There is one wrinkle worth knowing: when you use a link-local address as the next-hop, you MUST specify the exit interface, because link-local addresses are scoped per-interface. This lab configures IPv6 static routes between R1, R2, and R3 using both link-local and global next-hops, builds end-to-end IPv6 reachability across the base topology, and verifies with show ipv6 route.
Prerequisite: nf-05 needs to be done first, so that IPv6 routing is enabled and the addresses from the nf-05 addressing plan are configured on R1, R2, and R3.
What you will learn
- The
ipv6 routecommand syntax and how it differs fromip route - Why a link-local next-hop requires specifying an exit interface - and how to find the link-local address of YOUR R2 first
- The output format of
show ipv6 route- similar to IPv4 but with different code letters and the link-local detail - How to verify end-to-end IPv6 reachability across multiple static routes
What this lab does NOT cover
- IPv6 dynamic routing protocols (OSPFv3, EIGRP for IPv6). Covered in the IP Connectivity pillar.
- IPv6 default routes. Same syntax, just with
::/0as the destination. - IPv6 route summarization.
