Changes
→Specific aspects of venet network device
=== No possiblity to assign an IP from the CT ===
With venet device, only OpenVZ [[hardware node]] administrator can assign an IP address to a [[container]].
=== No packet sniffing support ===
Some applications using libpcap and similar packages will report an error.
=== No full support of IPv6 stack ===
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, to get your venet devices working.
Please have a look at the [[Quick installation#sysctl]] section.
You'll need to use the veth bridging device if you want full IPv6 compliance. See the [[VEs and HNs in same subnets]] article for an example.
== See also ==
