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:17] – samer | lab_with_ipv6_tunnel [2018/01/16 21:27] – samer | ||
---|---|---|---|
Line 5: | Line 5: | ||
[{{ : | [{{ : | ||
- | 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:// |
- | Hurricane Electric provides | + | Figure 2 illustrates |
- | {{ : | + | [{{ : |
+ | |||
+ | 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. The [[https:// | ||
+ | </ |
lab_with_ipv6_tunnel.txt · Last modified: 2018/01/19 19:25 by samer