IPv6 addressing, SLAAC and static routing
Enable IPv6 routing, address two routers (manual, EUI-64 and link-local), let the PCs autoconfigure with SLAAC, and route between the LANs with IPv6 static routes.
Scenario
The office is moving to dual stack. PC1 and PC2 are set to get their IPv6 addresses automatically (SLAAC), but nothing answers yet. Address the routers as planned: R1 LAN 2001:db8:1::1/64, the R1–R2 link 2001:db8:12::/64 (R1 .1, R2 .2), and R2's LAN 2001:db8:2::/64 using EUI-64. Give R1's link interface the easy-to-read link-local FE80::1, so R2 can use it as a next hop. Then add static routes so PC1 and PC2 can reach each other over IPv6.
Your tasks
- Both routers route IPv6.
- R1 has 2001:db8:1::1/64 on Gi0/0/0, 2001:db8:12::1/64 on Gi0/0/1, and link-local FE80::1 on Gi0/0/1.
- R2 has 2001:db8:12::2/64 on Gi0/0/0 and an EUI-64 address in 2001:db8:2::/64 on Gi0/0/1.
- PC1 and PC2 autoconfigure addresses in their LAN prefixes (SLAAC).
- PC1 and PC2 can ping each other over IPv6: R1 has a route to 2001:db8:2::/64 via 2001:db8:12::2, and R2 a default route via R1's link-local FE80::1.
The lab checks the result, not the exact commands. For example, a ping task passes only when the ping really succeeds through the network you built.