lab_with_ipv6_tunnel
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
lab_with_ipv6_tunnel [2018/01/16 21:37] – samer | lab_with_ipv6_tunnel [2018/01/16 21:54] – samer | ||
---|---|---|---|
Line 2: | Line 2: | ||
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. | 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. | ||
+ | |||
+ | ===== -. General Context ===== | ||
[{{ : | [{{ : | ||
Line 10: | Line 12: | ||
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. | 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 ===== | ||
[{{ : | [{{ : |
lab_with_ipv6_tunnel.txt · Last modified: 2018/01/19 19:25 by samer