Difference between revisions of "IPv6"
(possibly useful link to sixxs wiki.) |
(Documented venet static IPv6 configuration (opening paragraph leads users to think IPv6 won't work with venet)) |
||
| Line 3: | Line 3: | ||
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. | 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. 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 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 to 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== | ==See also== | ||
Revision as of 07:40, 10 February 2011
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.
Contents
venet example
(tests done on CentOS kernel 2.6.18-194.26.1.el5.028stab079.2)
Adding an IPv6 address to a container
# vzctl set <id> --ipadd <ipv6_addr> --save
In my tests, the container had to be restarted before it would respond to ICMP6 echo requests.
Removing an IPv6 address to a container
# vzctl set <id> --ipdel <ipv6_addr> --save
Removal is effective immediately and the host stops replying to echo requests.
See also
External Links
- A user success story / howto on SixXS wiki [1].
