Virtual network device - Revision history

95.24.137.24: /* Adding IP address to a container */

2013-02-10T16:59:24Z

‎Adding IP address to a container

Kir: Reverted edits by 212.138.69.17 (talk) to last revision by Kir

2011-11-28T05:35:44Z

Reverted edits by 212.138.69.17 (talk) to last revision by Kir

212.138.69.17: /* No full support of IPv6 stack */

2011-11-28T04:25:42Z

‎No full support of IPv6 stack

Kir: Reverted edits by 109.230.216.60 (talk) to last revision by 70.49.182.199

2011-11-28T03:30:01Z

Reverted edits by 109.230.216.60 (talk) to last revision by 70.49.182.199

109.230.216.60: kTrNUXaEeb

2011-11-28T02:52:55Z

kTrNUXaEeb

109.230.216.60: /* Usage */

2011-11-28T02:46:50Z

‎Usage

70.49.182.199: /* No packet sniffing support */

2011-04-21T06:41:37Z

‎No packet sniffing support

70.49.182.199: /* Specific aspects of venet network device */

2011-04-21T06:40:58Z

‎Specific aspects of venet network device

Cgb at 07:58, 10 February 2011

2011-02-10T07:58:11Z

Ginkyo: IPv6 support

2010-01-25T13:05:50Z

IPv6 support

@@ Line 24: / Line 24: @@
 vzctl set <CTID> --ipadd <IP1>[,<IP2>,...] [--save]
 </pre>
 {{Note|This option is incremental, so IP addresses are added to already existing ones.}}

@@ Line 64: / Line 64: @@
 Some applications using libpcap and similar packages will report an error.
-Thanks for the isnight. It brings light into the dark!
+=== No full support of IPv6 stack ===
 == See also ==

@@ Line 64: / Line 64: @@
 Some applications using libpcap and similar packages will report an error.
-=== No full support of IPv6 stack ===
+Thanks for the isnight. It brings light into the dark!
 == See also ==

← Older revision		Revision as of 03:30, 28 November 2011
Line 1:		Line 1:
−	~~As Charlie Sheen says~~, this ~~artilce~~ is ~~WINNING!~~	+	Virtual network device (<code>venet</code>) is the default network device for a [[container]]. 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.
		+
		+	== Usage ==
		+
		+	== Kernel module ==
		+	First of all, check that <code>vznetdev</code> module is loaded:
		+	<pre>
		+	# lsmod \| grep vznetdev
		+	</pre>
		+
		+	If it is not, load the module:
		+	<pre>
		+	# modprobe vznetdev
		+	</pre>
		+
		+	You might want to check /etc/init.d/vz script to make sure the module gets loaded during startup.
		+
		+	=== Adding IP address to a container ===
		+	<pre>
		+	vzctl set <CTID> --ipadd <IP1>[,<IP2>,...] [--save]
		+	</pre>
		+
		+	{{Note\|This option is incremental, so IP addresses are added to already existing ones.}}
		+
		+	==== Example ====
		+	<pre>
		+	vzctl set 101 --ipadd 10.0.0.1 --save
		+	vzctl 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.
		+
		+	=== Removing IP address from a container ===
		+	<pre>
		+	vzctl set <CTID> --ipdel <IP1>[,<IP2>,...] [--save]
		+	vzctl set <CTID> --ipdel all [--save]
		+	</pre>
		+
		+	==== Example ====
		+	<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.
		+
		+	== Specific aspects of venet network device ==
		+
		+	{{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).
		+
		+	=== No [[w:Network_bridge\|bridge]] support ===
		+	Venet network device cannot be bridged together and/or with other devices.
		+
		+	=== 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]].
		+
		+	=== Limited 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.
		+
		+	veth devices do require iptables and ip6tables exceptions on the host for each VE address.
		+
		+	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 ==
		+	* [[Veth]]
		+	* [[Differences between venet and veth]]
		+
		+	[[Category: Networking]]
		+	[[Category: HOWTO]]

← Older revision		Revision as of 02:52, 28 November 2011
Line 1:		Line 1:
−	~~Virtual network device (<code>venet</code>) is the default network device for a [[container]]. 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).	+	As Charlie Sheen says, this artilce is WINNING!
−
−	~~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.~~
−
−	~~Times are chiangng for the better if I can get this online~~!
−
−	~~== Kernel module ==~~
−	~~First of all, check that <code>vznetdev</code> module is loaded:~~
−	~~<pre>~~
−	~~# lsmod \| grep vznetdev~~
−	~~</pre>~~
−
−	~~If it is not, load the module:~~
−	~~<pre>~~
−	~~# modprobe vznetdev~~
−	~~</pre>~~
−
−	~~You might want to check /etc/init.d/vz script to make sure the module gets loaded during startup.~~
−
−	~~=== Adding IP address to a container ===~~
−	~~<pre>~~
−	~~vzctl set <CTID> --ipadd <IP1>[,<IP2>,...] [--save]~~
−	~~</pre>~~
−
−	~~{{Note\|This option is incremental, so IP addresses are added to already existing ones.}}~~
−
−	~~==== Example ====~~
−	~~<pre>~~
−	~~vzctl set 101 --ipadd 10.0.0.1 --save~~
−	~~vzctl 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.~~
−
−	~~=== Removing IP address from a container ===~~
−	~~<pre>~~
−	~~vzctl set <CTID> --ipdel <IP1>[,<IP2>,...] [--save]~~
−	~~vzctl set <CTID> --ipdel all [--save]~~
−	~~</pre>~~
−
−	~~==== Example ====~~
−	~~<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.
−
−	~~== Specific aspects of venet network device ==~~
−
−	~~{{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).~~
−
−	~~=== No [[w:Network_bridge\|bridge]] support ===~~
−	~~Venet network device cannot be bridged together and/or with other devices.~~
−
−	~~=== 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]].~~
−
−	~~=== Limited 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.~~
−
−	~~veth devices do require iptables and ip6tables exceptions on the host for each VE address.~~
−
−	~~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 ==~~
−	* [[Veth]]
−	* [[Differences between venet and veth]]
−
−	~~[[Category: Networking]]~~
−	~~[[Category: HOWTO]]~~

@@ Line 5: / Line 5: @@
 Venet device is created automatically on [[container]] start. Vzctl scripts set up an appropriate IP address and other settings on venet inside a container.
-==  Usage ==
+Times are chiangng for the better if I can get this online!
 == Kernel module ==

@@ Line 61: / Line 61: @@
 With venet device, only OpenVZ [[hardware node]] administrator can assign an IP address to a [[container]].
-=== No packet sniffing support ===
+=== Limited packet sniffing support ===
 Some applications using libpcap and similar packages will report an error.

@@ Line 60: / Line 60: @@
 === 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 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.
@@ Line 69: / Line 71: @@
 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 ==

@@ Line 29: / Line 29: @@
 ==== Example ====
 <pre>
-vzctl set 101 --ipadd 10.0.0.1 --save
+vzctl set 101 --ipadd 10.0.0.1  --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.
@@ Line 42: / Line 43: @@
 <pre>
 vzctl set 101 --ipdel 10.0.0.1
 </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.

@@ Line 1: / Line 1: @@
-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).
+Virtual network device (<code>venet</code>) is the default network device for a [[container]]. 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.
@@ Line 44: / Line 44: @@
 </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.
 == 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]] device (which have [[w:Data_Link_Layer|layer 2]] support.)}}
-=== No [[w:ARP|ARP]] protocol 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).
-=== No bridge support ===
+=== No [[w:Network_bridge|bridge]] support ===
 Venet network device cannot be bridged together and/or with other devices.
 === 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]].
 == See also ==