Differences

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

--- lab_with_ipv6_tunnel [2018/01/16 21:28] – samer
+++ lab_with_ipv6_tunnel [2018/01/16 21:37] – samer
@@ Line 9: / Line 9: @@
 In such case, tunnel mechanisms can help you get IPv6 connectivity without waiting for the migration of the IPv4-only network. [[https://tools.ietf.org/rfc/rfc7059.txt | RFC 7059]] presents an exhaustive overview of tunnel mechanisms. In this document, you will use a static 6in4 tunnel. Precisely, IPv6 packets generated by your lab devices are encapsulated in IPv4 headers in order to traverse the IPv4-only network. This IPv4 header is removed, and the original IPv6 packets are routed on the dual-stack Internet. The incoming packets will undergo a similar process to reach your lab devices.
-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.
+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}}]
@@ Line 29: / Line 29: @@
 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://www.cisco.com/c/en/us/support/docs/ip/access-lists/43920-iacl.html | configuration]] on a Cisco firewall uses the following syntax: ''access-list 101 permit 41 source destination''.
 </WRAP>
+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''.