Differences

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

--- lab_with_ipv6_tunnel [2018/01/16 22:32] – [1. General Context] samer
+++ lab_with_ipv6_tunnel [2018/01/16 22:32] – [1. General Context] samer
@@ Line 11: / Line 11: @@
 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 undergo a similar process to reach your lab devices.
-Figure 2 illustrates a deployment example of the 6in4 tunnel. In this example, the Tunnel End-Point (TEP) is a specific device that has IPv4 Internet connectivity on interface e1. The TEP adds and removes the encapsulating 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.
 ===== -. Tunnel Example Configuration =====