Virtual network device (<code>venet</code>) is the default network device for a [[container]]. This Due to [[w:Network_Layer|Layer 3]] employed by OpenVZ's venet, this network device looks like a point-to-point connection between [[container]] and the [[CT0|host system]]. It does packet switching based on IP header. This is a default network device for container (an alternative is [[veth]] device).

vzctl set 101 --ipadd 10.0.0.1 --savevzctl set 101 --ipadd fd00::101 --save

== Sysctl Specific aspects of venet network device ==

You will need to configure some sysctl parameters to get your {{Note|If you require a feature which venet devices working.Please is lacking (from the list below), please consider using [[veth]] device (which have a look at the [[Installation_on_Debian#sysctlw:Data_Link_Layer|layer 2]] sectionsupport.)}}

== IPv6 =No [[w:Address_Resolution_Protocol|ARP]] protocol support ===Venet network device is explicitly NOARP, so there is no MAC address.Consequently, it's not possible to make broadcasts inside a [[container]], so software like Samba server or DHCP server will not function (under a container with a venet network device).

To setup IPv6 networking with venet you'll need to enable the following in your sysctl.conf=== No [[w: <code> # IPv6 Packet Forwarding and Proxy NDP net.ipv6.conf.default.forwarding Network_bridge|bridge]] support = 1 net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.default.proxy_ndp = 1 net.ipv6.conf.allVenet network device cannot be bridged together and/or with other devices.proxy_ndp = 1</code>

In === No full support of IPv6 you stack ===venet devices are not fully IPv6 compliant. They do not properly support MAC addresses and consequently link local addresses and can't control not play nice with neighbor discovery or router advertisements, router discovery, or auto-conf. They also require additional modifications to the layer 3 forwarding per devicebehaviour of the host via sysctl, forwarding control has to take place in ip6tables, so all interfaces will forward IPv6 trafficget your venet devices working.Please have a look at the [[Quick installation#sysctl]] section.

If you enable IPv6 forwarding veth devices do require iptables and ip6tables exceptions on the host for your interfaces, Linux assumes your host to act like a router and will ignore 'Router Advertisments' (see [http://en.wikipedia.org/wiki/Neighbor_Discovery_Protocol Neighbor Discovery Protocol] or [http://mirrors.bieringer.de/Linux+IPv6-HOWTO/proc-sys-net-ipv6.html Linux IPv6 Howto])each VE address.

You will as well 'll need to configure a new v6 default gateway for your host: <code> ip addr add 2620:0:2d0:1::193/64 dev eth0 route -6 add default gw 2620:0:2d0:1::1</code> You can add these commands to your existing network configuration on Debian/Linux: <code> iface eth0 inet static address 64.131.90.7 netmask 255.255.255.240 network 64.131.90.0 broadcast 64.131.90.15 gateway 64.131.90.1 up ip addr add 2620:0:2d0:1::193/64 dev eth0 up route -6 add default gw 2620:0:2d0:1::1 down ip addr del 3620:0:2d0:1::193/64 dev eth0</code>== Specific aspects of venet network device == === No [http://en.wikipedia.org/wiki/Address_Resolution_Protocol ARP] protocol support ===Venet network device is explicitly NOARP, so there is no MAC address.Consequently, it's not possible to make broadcasts inside a [[CT|container]], so software like Samba server or DHCP server, will not function (under a container with a venet network device).<br />Please consider use of [[the veth]] network bridging device if you need this feature === No bridge support ===Venet network device cannot be bridged together and/or with other deviceswant full IPv6 compliance.<br />Please consider use of [[veth]] network device if you need this feature === No possiblity to assign an IP from See the CT ===With venet device, only OpenVZ [[Hardware_Node|hardware nodeVEs and HNs in same subnets]] administrator can assign article for an IP address to a [[CT|container]]example.<br />Please consider use of [[veth]] network device if you need this feature