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 [2018/01/16 21:37] – samer | lab_with_ipv6_tunnel [2018/01/16 22:42] – [3. Lab Platform Configuration] 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 7: | Line 9: | ||
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, | 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:// | + | 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. 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 ===== | ||
+ | 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. | ||
[{{ : | [{{ : | ||
- | Hurricane Electric provides a free service for 6in4 tunnels. Subscription is available on [[https:// | + | Hurricane Electric provides a free service for 6in4 tunnels. Subscription is available on [[https:// |
<code bash> | <code bash> | ||
Line 21: | Line 24: | ||
netmask 64 | netmask 64 | ||
endpoint # | endpoint # | ||
- | local #TEP_IPv4_address | + | local #TEP_e1_IPv4_address |
ttl 255 | ttl 255 | ||
gateway # | gateway # | ||
Line 30: | Line 33: | ||
</ | </ | ||
- | Now, you can verify the configuration of your interface '' | + | Now, you can verify the configuration of your tunnel |
+ | ===== -. Lab Platform Configuration ===== | ||
+ | Hurricane Electric has automatically assigned a /64 prefix to your account and routed it to the '' | ||
+ | ==== -. Static Configuration ==== | ||
+ | ==== -. Stateless Auto-Configuration ==== |
lab_with_ipv6_tunnel.txt · Last modified: 2018/01/19 19:25 by samer