Differences

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

--- lab_with_ipv6_tunnel [2018/01/16 20:17] – samer
+++ lab_with_ipv6_tunnel [2018/01/16 20:34] – samer
@@ Line 5: / Line 5: @@
 [{{ :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.
+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.
+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 on the dual-stack Internet. The incoming packets will undergo a similar process to reach your lab devices.
+Figure 2 illustrates a deployment example of the 6in4 tunnel. The Tunnel End-Point (TEP) adds and removes the IPv4 headers. Therefore, a specific configuration should be applied on this device. Moreover, you can choose this device to be the default gateway for your lab in a way that all ongoing IPv6 trafic benefits from the tunnelling mechanism.
+[{{ :ipv6-tunnel-2.png?nolink&600 | Figure 2. 6in4 Tunnel for extending IPv6 connectivity}}]
 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 |}}