Differences

This shows you the differences between two versions of the page.

--- lab_with_ipv6_tunnel [2017/12/13 10:06] – created samer
+++ lab_with_ipv6_tunnel [2018/01/16 20:17] – samer
@@ Line 1: / Line 1: @@
 ====== Lab with IPv6 Tunnel ======
-This document explains how to bring connectivity to a lab platform
+This document explains how to bring IPv6 Internet connectivity to a lab platform using tunnels. This scenario is useful whenever IPv6 is not enabled on the Internet access of your Lab.
+[{{ :ipv6-tunnel-1.png?nolink&600 | Figure 1. Internet connectivity and IPv6 support}}]
+As shown in Figure 1, we suppose that your lab is equipped with either dual-stack (supporting IPv4 and IPv6) devices or IPv6-only devices. In order to get IPv6 connectivity to your lab, you need to traverse a legacy IPv4 only network. Unfortunately, this is still the case for many internet service providers around the world.
+In such case, tunnel mechanisms can help you get IPv6 connectivity without waiting for the migration of the IPv4-only network. [[https://tools.ietf.org/rfc/rfc7059.txt | RFC 7059]] presents an exhaustive overview of tunnel mechanisms. In this document, you will use a static 6in4 tunnel. Precisely, IPv6 packets generated by your lab devices are encapsulated in IPv4 headers in order to traverse the IPv4-only network. This IPv4 header is removed, and the original IPv6 packets are routed in the dual-stack Internet.
+Hurricane Electric provides a free service for 6in4 tunnels. Subscription is available on [[https://tunnelbroker.net]]. You will need to create a ''Regular Tunnel''.
+{{ :ipv6-tunnel-2.png?nolink&600 |}}