We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is Why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 637 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

367 New Members signed up the last 30 days!

satisfaction-guaranteed

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Tags: ,


Forum Replies

  1. IPv6 uses the link-local addresses as the next-hop for routing entries so there is no need to configure a “global” IPv6 address.

  2. If you need some help with this, it’s best to your topology and configs on the GNS3Vault forum. We can take a look there…

  3. The major differences:

    MCT - MTU is 1480, less overhead, supports only a single passenger protocol, mode is ipv6ip.

    GRE - MTU is 1476, more overhead, supports multiple passenger protocols, mode is gre.

  4. Rene, I tried using the following lab without configuring a global IPv6 address but it would not work until I configured the global IPv6 address. I’m going to continue to play with this to see if I can figure it out, but in the event I don’t can you tell me if there’s something else I have to do to get this to work with the link-local addresses?

    https://gns3vault.com/ipv6/ipv6-tunneling-over-ipv4/

  5. It has. Thank you very much for your reply!

14 more replies! Ask a question or join the discussion by visiting our Community Forum