A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
! Enable IPv6 routing firstR1(config)# ipv6 unicast-routing! Static route with global unicast next-hopR1(config)# ipv6 route 2001:db8:2::/64 2001:db8:1::2! Static route with link-local next-hop — MUST specify egress interfaceR1(config)# ipv6 route 2001:db8:3::/64 gigabitEthernet0/1 fe80::2! Default routeR1(config)# ipv6 route ::/0 2001:db8:1::ffff! Default via link-localR1(config)# ipv6 route ::/0 gigabitEthernet0/0 fe80::1
IPv6 static route syntax mirrors IPv4, but the `::/0` default is shorter than `0.0.0.0/0`. And you must remember to enable `ipv6 unicast-routing` first — without it, no route installs and interfaces won't accept global addresses.
When the next-hop is a link-local address (`fe80::`), you MUST specify the egress interface. Link-local addresses are only unique on a single link — the router has no way to know which interface to use without explicit direction. This is the #1 source of IPv6 static route errors.
The Codes section shows both `ND` (Neighbor Discovery default — learned from Router Advertisement) and `NDp` (ND prefix — learned from RA prefix). These are the IPv6-specific dynamic route sources you won't see in IPv4.
! Instead of many /64 statics, use a single summary! Sites use 2001:db8:0001::/48 through 2001:db8:000f::/48R1(config)# ipv6 route 2001:db8::/32 2001:db8:1::2! Verify — the summary replaces many specific routesR1# show ipv6 route static
IPv6 aggregation is easier than IPv4 because the address space is so vast that /48s and /32s are common. A single /32 summary can cover an entire organization's allocations. This makes IPv6 routing tables dramatically smaller than their IPv4 equivalents.
Finish the lesson once you have worked through the material. This awards ★ 30 XP.