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 19:21] – [1. General Context] samerlab_with_ipv6_tunnel [2018/01/19 19:25] (current) – [3.2. Stateless Auto-Configuration] samer
Line 32: 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 the /64 prefix you are assigned.+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 your /64 routed prefix (as shown on the Tunnel details information page). Moreover, you should add a default route using the link-local address of the interface e0 of TEP as in the following:+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
Line 48: Line 48:
 ==== -. Stateless Auto-Configuration ==== ==== -. 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 (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 install radvd using ''apt-get install radvd'' on the TEP and configure the /64 prefix in ''/etc/radvd.conf'' as follows:  You can install radvd using ''apt-get install radvd'' on the TEP and configure the /64 prefix in ''/etc/radvd.conf'' as follows: 
      
lab_with_ipv6_tunnel.1516386061.txt.gz · Last modified: 2018/01/19 19:21 by samer