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 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 63: | Line 61: | ||
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]]. | ||
− | === | + | === 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. | 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. | Please have a look at the [[Quick installation#sysctl]] section. | ||
Line 73: | Line 69: | ||
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. | 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 == | == See also == |