IPv6 6to4 Tunneling... NO STATIC ROUTE?!

So I finally got this working, with the lab from my previous post. Here's a 6to4 tunnel, without the 2002::/16 static route, or ANY static routes for that matter.

More IPv6 Tunneling

So moving on from my last post, and before doing a little write up on IPv6 tunneling I thought I'd do one more scenario. So very similar to the last issue, we have an IPv4 only WAN and we want to dynamically tunnel IPv6 traffic over said WAN.

Restrictions/Requirements:
- Do not modify tunnel mode
- Do not add any additional static routes
- Do not introduce an IPv6 dynamic routing
- When the task is complete you should be able to successfully ping 2002:A0A:A02::1:2 and 2002:A0A:A03::1:3 on R1 sourcing from Lo0.


GNS3 Files: Here


Diagram: 

Solution:

IPv6 Tunneling... you might hate this one.

So, I'm going to [try] and do this one a little different. I want to start with my typical, arguably lazy approach of presenting a problem and posting a video solution. However, for fun I'll do a closer look follow up to this one in a separate post. So here's the task at hand, your organization is looking to start migrating to IPv6. Currently your MPLS provider does not support IPv6, but part of this testing phase is communication between sites. Your goal is to maintain a fully meshed environment, with minimal tunnel interfaces.

Requirements/Restrictions:
- Create only a single tunnel interface on each edge router
- Do not add any IPv6 addresses to any physical interfaces.
- You may add a single static IPv6 route, but this is not ideal. [attempt to avoid this]
- Routing should take the most efficient path possible. (I.e. don't send traffic from R1 to R3 through R2)
- When you're done, all routers should be able to ping each others look backs. Use only EIGRPv6 to accomplish this. *Due to some IOS restrictions, you maybe use OSPFv3 if EIGRP is not supported on your platform
- Do not modify the MPLS router

GNS3 here

Diagram:

Solution: