lab_with_ipv6_tunnel
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
lab_with_ipv6_tunnel [2017/12/13 10:52] – samer | lab_with_ipv6_tunnel [2018/01/16 20:34] – samer | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Lab with IPv6 Tunnel ====== | ====== Lab with IPv6 Tunnel ====== | ||
- | 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 | + | 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. |
- | {{ : | + | [{{ : |
+ | |||
+ | 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, | ||
+ | |||
+ | In such case, tunnel mechanisms can help you get IPv6 connectivity without waiting for the migration of the IPv4-only network. [[https:// | ||
+ | |||
+ | 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. | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | Hurricane Electric provides a free service for 6in4 tunnels. Subscription is available on [[https:// | ||
- | [[https:// |
lab_with_ipv6_tunnel.txt · Last modified: 2018/01/19 19:25 by samer