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:28] – 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 9: | Line 11: | ||
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. | + | Figure 2 illustrates a deployment example of the 6in4 tunnel. |
+ | |||
+ | ===== -. Tunnel Example Configuration ===== | ||
[{{ : | [{{ : | ||
Line 27: | Line 31: | ||
<WRAP center round tip 100%> | <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:// | + | 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 interface '' |
lab_with_ipv6_tunnel.txt · Last modified: 2018/01/19 19:25 by samer