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 20:34] – samer | ||
---|---|---|---|
Line 5: | Line 5: | ||
[{{ : | [{{ : | ||
- | 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 |
- | [[https:// | + | In such case, tunnel mechanisms can help you get IPv6 connectivity without waiting for the migration of the IPv4-only network. |
+ | |||
+ | Figure 2 illustrates a deployment example of the 6in4 tunnel. The Tunnel End-Point (TEP) adds and removes the 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:// | Hurricane Electric provides a free service for 6in4 tunnels. Subscription is available on [[https:// | ||
- | {{ : |
lab_with_ipv6_tunnel.txt · Last modified: 2018/01/19 19:25 by samer