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 revision
Previous revision
lab_with_ipv6_tunnel [2018/01/19 11:47] – [3.2. Stateless Auto-Configuration] samerlab_with_ipv6_tunnel [2018/01/19 19:25] (current) – [3.2. Stateless Auto-Configuration] samer
Line 7: Line 7:
 [{{ :ipv6-tunnel-1.png?nolink&600 | Figure 1. Internet connectivity and IPv6 support}}] [{{ :ipv6-tunnel-1.png?nolink&600 | Figure 1. Internet connectivity and IPv6 support}}]
  
-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, this is still the case for many Internet Service Providers around the world. +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 ===== ===== -. Tunnel Example Configuration =====
Line 33: Line 32:
 </WRAP> </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 ===== ===== -. 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. 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.
  
 +In both cases, you should start by configuring a static IPv6 address on interface e0 of the TEP. This address should be chosen from your assigned /64 prefix.
 <code bash> <code bash>
 ip -6 addr add Routed_Prefix::1/64 dev e0 ip -6 addr add Routed_Prefix::1/64 dev e0
 </code> </code>
 ==== -. Static Configuration ==== ==== -. Static Configuration ====
-On PC in your lab, you can configure a static IPv6 address chosen from the /64 routed prefix (as shown on the Tunnel details information page). Moreover, you shroud add a default route using the link-local address of the interface e0 of TEP.+On any PC in your lab, you can configure a static IPv6 address chosen from your /64 routed prefix. Moreover, you should add a default route using the link-local address of the e0 interface of the TEP as in the following:
 <code bash> <code bash>
 ip -6 addr add Routed_Prefix::X/64 dev PC_interface ip -6 addr add Routed_Prefix::X/64 dev PC_interface
 ip -6 route add default via TEP_e0_link_local_IPv6_addr ip -6 route add default via TEP_e0_link_local_IPv6_addr
 </code> </code>
- 
 ==== -. Stateless Auto-Configuration ==== ==== -. Stateless Auto-Configuration ====
  
-If you want to benefit for the auto-configuration mechanisms in IPv6, you can start a routing daemon on TEP. This daemon (typical radvd on Debian) will send routing advertisements and enable your lab PC to perform stateless auto-configuration. +If you want to benefit from the auto-configuration mechanisms in IPv6, you can start a routing daemon on the TEP. This daemon (typically radvd on Debian) will send routing advertisements and enable your lab PC to perform stateless auto-configuration. 
-You can instal radvd using ''apt-get install radvd'' on the TEP and configure the /64 prefix in ''/etc/radvd.conf'' as in the following+You can install radvd using ''apt-get install radvd'' on the TEP and configure the /64 prefix in ''/etc/radvd.conf'' as follows
      
 <code bash>   <code bash>  
Line 62: Line 61:
  };  };
 }; };
-<code>   +</code>   
-/etc/init.d/radvd+ 
 +Now you can start the routing daemon on the TEP using ''/etc/init.d/radvd start'' and observe the auto-configuration on any PC in you local network.
lab_with_ipv6_tunnel.1516358859.txt.gz · Last modified: 2018/01/19 11:47 by samer