Differences

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

--- lab_with_ipv6_tunnel [2018/01/19 19:19] – [1. General Context] samer
+++ lab_with_ipv6_tunnel [2018/01/19 19:22] – [2. Tunnel Example Configuration] samer
@@ Line 9: / Line 9: @@
 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. We also suppose that you have no direct Internet IPv6 connectivity since you need to traverse a legacy IPv4-only access network. Unfortunately, this is still the case for many Internet Service Providers around the world.
-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 undergo a similar process to reach your lab devices.
+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 to the IPv6 destination. The incoming packets undergo a similar process to reach your lab devices.
 ===== -. Tunnel Example Configuration =====
@@ Line 33: / Line 32: @@
 </WRAP>
-Now, you can verify the configuration of your tunnel 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 tunnel 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 =====
 Hurricane Electric has automatically assigned a /64 prefix to your account and routed it to the ''Client IPv6 Address''. You can retrieve the address on the tunnel details page under the ''Routed IPv6 Prefixes'' section. This prefix allows your TEP to operate as the router for this prefix and allows you to utilize static or automatic configuration  to hand out IPs from this allocation to your internal network. In the following, we will examine these two methods.