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 11:21] – samer | lab_with_ipv6_tunnel [2018/01/19 11:43] – [3.1. Static Configuration] samer | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== IPv6 in a 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 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. | ||
- | {{ :ipv6-tunnel-1.png? | + | ===== -. General Context ===== |
- | [[https://tools.ietf.org/ | + | [{{ :ipv6-tunnel-1.png? |
- | Hurricane Electric provides a free service for 6in4 tunnels. Subscription | + | 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 |
- | {{ : | + | In such case, tunnel mechanisms can help you get IPv6 connectivity without waiting for the migration of the IPv4-only network. [[https:// |
+ | |||
+ | |||
+ | ===== -. 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:// | ||
+ | |||
+ | <code bash> | ||
+ | auto he-ipv6 | ||
+ | iface he-ipv6 inet6 v4tunnel | ||
+ | address # | ||
+ | netmask 64 | ||
+ | endpoint # | ||
+ | local # | ||
+ | ttl 255 | ||
+ | gateway # | ||
+ | </ | ||
+ | |||
+ | <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:// | ||
+ | </ | ||
+ | |||
+ | Now, you can verify the configuration of your tunnel interface '' | ||
+ | ===== -. Lab Platform Configuration ===== | ||
+ | Hurricane Electric has automatically assigned a /64 prefix to your account and routed it to the '' | ||
+ | |||
+ | <code bash> | ||
+ | ip -6 addr add Routed_Prefix:: | ||
+ | </ | ||
+ | ==== -. Static Configuration ==== | ||
+ | On a PC in your lab, you can configure a static IPv6 address chosen from the /64 routed prefix (as shown on the Tunnel details information page). Moreover, you shroud add a default route using the link-local address of the interface e0 of TEP. | ||
+ | <code bash> | ||
+ | ip -6 addr add Routed_Prefix:: | ||
+ | ip -6 route add default via TEP_e0_link_local_IPv6_addr | ||
+ | </ | ||
+ | |||
+ | ==== -. Stateless Auto-Configuration ==== | ||
+ | |||
+ | interface eth1 | ||
+ | { | ||
+ | AdvSendAdvert on; | ||
+ | prefix 2001: | ||
+ | { | ||
+ | AdvOnLink on; | ||
+ | AdvAutonomous on; | ||
+ | }; | ||
+ | }; | ||
+ | |||
+ | / |
lab_with_ipv6_tunnel.txt · Last modified: 2018/01/19 19:25 by samer