Editing Virtual network device
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | Virtual network device (<code>venet</code>) is the default network device for a [[container]]. | + | Virtual network device (<code>venet</code>) is the default network device for a [[container]]. 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 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. | ||
Line 24: | Line 24: | ||
vzctl set <CTID> --ipadd <IP1>[,<IP2>,...] [--save] | vzctl set <CTID> --ipadd <IP1>[,<IP2>,...] [--save] | ||
</pre> | </pre> | ||
− | |||
− | |||
{{Note|This option is incremental, so IP addresses are added to already existing ones.}} | {{Note|This option is incremental, so IP addresses are added to already existing ones.}} | ||
Line 31: | Line 29: | ||
==== Example ==== | ==== Example ==== | ||
<pre> | <pre> | ||
− | vzctl set 101 --ipadd 10.0.0.1 | + | vzctl set 101 --ipadd 10.0.0.1 --save |
− | |||
</pre> | </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. | 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. | ||
Line 45: | Line 42: | ||
<pre> | <pre> | ||
vzctl set 101 --ipdel 10.0.0.1 | vzctl set 101 --ipdel 10.0.0.1 | ||
− | |||
</pre> | </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. | 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 [[Quick installation#sysctl]] section. | ||
+ | |||
+ | == IPv6 == | ||
+ | |||
+ | venet does not fully support IPv6. 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. | ||
== Specific aspects of venet network device == | == Specific aspects of venet network device == | ||
− | {{Note|If you require a feature which venet is lacking (from the list below), please consider using [[veth]] | + | {{Note|If you require a feature which venet is lacking (from the list below), please consider using [[veth]].}} |
− | === No [[w: | + | === No [[w:ARP|ARP]] protocol support === |
Venet network device is explicitly NOARP, so there is no MAC address. | 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). | 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). | ||
− | === No | + | === No bridge support === |
Venet network device cannot be bridged together and/or with other devices. | Venet network device cannot be bridged together and/or with other devices. | ||
=== No possiblity to assign an IP from the CT === | === 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]]. | With venet device, only OpenVZ [[hardware node]] administrator can assign an IP address to a [[container]]. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== See also == | == See also == |