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 22:34] – [2. Tunnel Example Configuration] samer | lab_with_ipv6_tunnel [2018/01/19 19:19] – [1. General Context] 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. | ||
Line 7: | Line 7: | ||
[{{ : | [{{ : | ||
- | 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. | + | 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 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:// | ||
Line 35: | Line 35: | ||
Now, you can verify the configuration of your tunnel interface '' | Now, you can verify the configuration of your tunnel interface '' | ||
===== -. Lab Platform Configuration ===== | ===== -. Lab Platform Configuration ===== | ||
+ | Hurricane Electric has automatically assigned a /64 prefix to your account and routed it to the '' | ||
+ | |||
+ | In both cases, you should start by configuring a static IPv6 address on interface e0 of the TEP. This address should be chosen from the /64 prefix you are assigned. | ||
+ | <code bash> | ||
+ | ip -6 addr add Routed_Prefix:: | ||
+ | </ | ||
==== -. Static Configuration ==== | ==== -. Static Configuration ==== | ||
+ | On a PC in your lab, you can configure a static IPv6 address chosen from your /64 routed prefix (as shown on the Tunnel details information page). Moreover, you should add a default route using the link-local address of the interface e0 of TEP as in the following: | ||
+ | <code bash> | ||
+ | ip -6 addr add Routed_Prefix:: | ||
+ | ip -6 route add default via TEP_e0_link_local_IPv6_addr | ||
+ | </ | ||
==== -. Stateless Auto-Configuration ==== | ==== -. Stateless Auto-Configuration ==== | ||
+ | |||
+ | If you want to benefit from the auto-configuration mechanisms in IPv6, you can start a routing daemon on the TEP. This daemon (typical radvd on Debian) will send routing advertisements and enable your lab PC to perform stateless auto-configuration. | ||
+ | You can install radvd using '' | ||
+ | | ||
+ | <code bash> | ||
+ | interface eth1 | ||
+ | { | ||
+ | AdvSendAdvert on; | ||
+ | prefix 2001: | ||
+ | { | ||
+ | AdvOnLink on; | ||
+ | AdvAutonomous on; | ||
+ | }; | ||
+ | }; | ||
+ | </ | ||
+ | |||
+ | Now you can start the routing daemon on the TEP using ''/ |
lab_with_ipv6_tunnel.txt · Last modified: 2018/01/19 19:25 by samer