From OpenVZ Virtuozzo Containers Wiki
|
|
| Line 1: |
Line 1: |
| − | [[Category:HOWTO]]
| + | Boy that relaly helps me the heck out. |
| − | [[Category:Networking]]
| |
| − | IPv6 works best when veth devices are used to bridge VEs to their host. An IPv6 compliant method of using veth interfaces for VEs can be found in the [[VEs and HNs in same subnets]] article.
| |
| − | | |
| − | venet devices are not fully IPv6 compliant, but still works if you statically assign IPv6 addresses. They do not properly support MAC addresses and consequently link local addresses and can not play nice with neighbor discovery or router advertisements, router discovery, or auto-conf. They also require additional modifications to the layer 3 forwarding behaviour of the host via sysctl.
| |
| − | | |
| − | == venet example ==
| |
| − | (tests done on CentOS kernel 2.6.18-194.26.1.el5.028stab079.2)
| |
| − | | |
| − | === Adding an IPv6 address to a container ===
| |
| − | <pre>
| |
| − | # vzctl set <id> --ipadd <ipv6_addr> --save
| |
| − | </pre>
| |
| − | | |
| − | In my tests, the container had to be restarted before it would respond to ICMP6 echo requests.
| |
| − | | |
| − | === Removing an IPv6 address from a container ===
| |
| − | <pre>
| |
| − | # vzctl set <id> --ipdel <ipv6_addr> --save
| |
| − | </pre>
| |
| − | | |
| − | Removal is effective immediately and the host stops replying to echo requests.
| |
| − | | |
| − | ==See also==
| |
| − | * [[Virtual Ethernet device]]
| |
| − | * [[Differences between venet and veth]]
| |
| − | | |
| − | == External Links ==
| |
| − | * A user success story / howto on SixXS wiki [https://www.sixxs.net/wiki/User:JNN2-SIXXS/OpenVZ].
| |
Revision as of 04:04, 28 November 2011
Boy that relaly helps me the heck out.
