lab_with_ipv6_tunnel
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
lab_with_ipv6_tunnel [2018/01/17 19:59] – [3.2. Stateless Auto-Configuration] samer | lab_with_ipv6_tunnel [2018/01/19 11:47] – [3.2. Stateless Auto-Configuration] samer | ||
---|---|---|---|
Line 41: | Line 41: | ||
</ | </ | ||
==== -. Static Configuration ==== | ==== -. Static Configuration ==== | ||
+ | On a 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. | ||
<code bash> | <code bash> | ||
ip -6 addr add Routed_Prefix:: | ip -6 addr add Routed_Prefix:: | ||
ip -6 route add default via TEP_e0_link_local_IPv6_addr | ip -6 route add default via TEP_e0_link_local_IPv6_addr | ||
</ | </ | ||
- | |||
==== -. 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. | ||
+ | You can instal radvd using '' | ||
+ | | ||
+ | <code bash> | ||
interface eth1 | interface eth1 | ||
{ | { | ||
Line 59: | Line 62: | ||
}; | }; | ||
}; | }; | ||
+ | < | ||
/ | / |
lab_with_ipv6_tunnel.txt · Last modified: 2018/01/19 19:25 by samer