Changes
→Adding IP address to a container
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). Venet drop ip-packets '''from''' the container with a source address, and '''in''' the container with the destination address, which is not corresponding to an ip-address of the container.
Venet device is created automatically on [[container]] start. Vzctl scripts set up an appropriate IP address and other settings on venet inside a container.
vzctl set <CTID> --ipadd <IP1>[,<IP2>,...] [--save]
</pre>
Address can optionally have a netmask specified in the CIDR notation (e.g. 10.1.2.3/25).
{{Note|This option is incremental, so IP addresses are added to already existing ones.}}
==== Example ====
<pre>
vzctl set 101 --ipadd 10.0.0.1 --savevzctl set 101 --ipadd fd00::101 --save
</pre>
After executing this command IP address 10.0.0.1 will be added to container 101 and IP configuration will be saved to a container configuration file.
<pre>
vzctl set 101 --ipdel 10.0.0.1
vzctl set 101 --ipdel fd00::101
</pre>
After executing this command IP address 10.0.0.1 will be removed from container 101, but IP configuration will not be changed in container config file. And after container reboot IP address 10.0.0.1 will be assigned to this container again.
== Sysctl == You will need to configure some sysctl parameters to get your venet devices working.Please have a look at the [[Installation_on_Debian#sysctl]] section. == IPv6 == To setup IPv6 networking with Specific aspects of venet you'll need to enable the following in your sysctl.conf: <code> net.ipv6.conf.default.forwarding network device = 1 net.ipv6.conf.all.forwarding = 1</code>
{{Note|If you require a feature which venet is lacking (from the list below), please consider using [[veth]] device (which have [[w:Data_Link_Layer|layer 2]] support.)}}
=== 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).
== See also ==