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 20:06] – samer | lab_with_ipv6_tunnel [2018/01/16 22:32] – [1. General Context] 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 ===== | ||
[{{ : | [{{ : | ||
- | As shown in Figure 1, we suppose that your lab is equipped with either dual-stack (support | + | As shown in Figure 1, we suppose that your lab is equipped with either dual-stack (supporting |
+ | |||
+ | 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 ===== | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | Hurricane Electric provides a free service | ||
+ | |||
+ | <code bash> | ||
+ | auto he-ipv6 | ||
+ | iface he-ipv6 inet6 v4tunnel | ||
+ | address # | ||
+ | netmask 64 | ||
+ | endpoint # | ||
+ | local # | ||
+ | ttl 255 | ||
+ | gateway # | ||
+ | </ | ||
- | [[https://tools.ietf.org/rfc/rfc7059.txt | RFC 7059]] presents an overview of tunnel mechanisms. In this document, you will use a static 6in4 tunnel. | + | <WRAP center round tip 100%> |
+ | When behind a firewall appliance, make sure that protocol 41 is not filtered. Note well that 41 is the IPv6 protocol number encapsulated in IPv4 (and not a port number) and should be authorized. For instance, the [[https://www.cisco.com/c/en/ | ||
+ | </ | ||
- | Hurricane Electric provides a free service for 6in4 tunnels. Subscription is available | + | Now, you can verify the configuration of your interface '' |
- | {{ :ipv6-tunnel-2.png? | + | ===== -. Lab Platform Configuration ===== |
+ | ==== -. Static Configuration ==== | ||
+ | ==== -. Stateless Auto-Configuration ==== |
lab_with_ipv6_tunnel.txt · Last modified: 2018/01/19 19:25 by samer