wikiroute

networking recipes

User Tools

Site Tools


lab_with_ipv6_tunnel

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
lab_with_ipv6_tunnel [2018/01/16 22:32] – [1. General Context] samerlab_with_ipv6_tunnel [2018/01/16 22:32] – [2. Tunnel Example Configuration] samer
Line 13: Line 13:
  
 ===== -. Tunnel Example Configuration ===== ===== -. 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.
 [{{ :ipv6-tunnel-2.png?nolink&600 | Figure 2. 6in4 Tunnel for extending IPv6 connectivity}}] [{{ :ipv6-tunnel-2.png?nolink&600 | Figure 2. 6in4 Tunnel for extending IPv6 connectivity}}]
  
Line 34: Line 34:
  
 Now, you can verify the configuration of your interface ''ip -6 addr show dev he-ipv6'' on the TEP and test if the IPv6 connectivity is working ''ping6 ipv6.google.com''. Now, you can verify the configuration of your interface ''ip -6 addr show dev he-ipv6'' on the TEP and test if the IPv6 connectivity is working ''ping6 ipv6.google.com''.
- 
 ===== -. Lab Platform Configuration ===== ===== -. Lab Platform Configuration =====
 ==== -. Static Configuration ==== ==== -. Static Configuration ====
 ==== -. Stateless Auto-Configuration ==== ==== -. Stateless Auto-Configuration ====
lab_with_ipv6_tunnel.txt · Last modified: 2018/01/19 19:25 by samer