OpenVZ Virtuozzo Containers Wiki - User contributions [en]

Virtual network device

2009-05-28T07:50:56Z

Sts: /* IPv6 */

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 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
</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
</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 venet you'll need to enable the following in your sysctl.conf:

<code>
# IPv6 Packet Forwarding and Proxy NDP
net.ipv6.conf.default.forwarding = 1
net.ipv6.conf.all.forwarding = 1
net.ipv6.conf.default.proxy_ndp = 1
net.ipv6.conf.all.proxy_ndp = 1
</code>

In IPv6 you can't control forwarding per device, forwarding control has to take place in ip6tables, so all interfaces will forward IPv6 traffic.

If you enable IPv6 forwarding 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]).

You will as well 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>

== See also ==
* [[Veth]]
* [[Differences between venet and veth]]

[[Category: Networking]]
[[Category: HOWTO]]

Virtual network device

2009-01-05T13:32:49Z

Sts: /* IPv6 */

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 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
</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
</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 venet you'll need to enable the following in your sysctl.conf:

<code>
net.ipv6.conf.default.forwarding = 1
net.ipv6.conf.all.forwarding = 1
</code>

In IPv6 you can't control forwarding per device, forwarding control has to take place in ip6tables, so all interfaces will forward IPv6 traffic.

If you enable IPv6 forwarding 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]).

You will as well 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>

== See also ==
* [[Veth]]
* [[Differences between venet and veth]]

[[Category: Networking]]
[[Category: HOWTO]]

Virtual network device

2009-01-05T13:29:10Z

Sts: /* IPv6 */

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 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
</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
</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 venet you'll need to enable the following in your sysctl.conf:

<code>
net.ipv6.conf.default.forwarding = 1
net.ipv6.conf.all.forwarding = 1
</code>

In IPv6 you can't control forwarding per device, forwarding control has to take place in ip6tables, so all interfaces will forward IPv6 traffic.

If you enable IPv6 forwarding 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]).

You will as well 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>

== See also ==
* [[Veth]]
* [[Differences between venet and veth]]

[[Category: Networking]]
[[Category: HOWTO]]

Virtual network device

2009-01-05T13:26:03Z

Sts: /* IPv6 */

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 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
</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
</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 venet you'll need to enable the following in your sysctl.conf:

<code>
net.ipv6.conf.default.forwarding = 1
net.ipv6.conf.all.forwarding = 1
</code>

In IPv6 you can't control forwarding per device, forwarding control has to take place in ip6tables, so all interfaces will forward IPv6 traffic.

If you enable IPv6 forwarding 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]).

You will as well need to configure a new v6 default gateway for your host:

<code>
ip addr add 2001:1:1:1:0::2/64 dev eth0
route -6 add default gw 2001:1:1:1:0::1
</code>

You can add these commands to your existing network configuration on Debian/Linux:

<code>
iface eth0 inet static
address 213.235.253.206
netmask 255.255.255.240
network 213.235.253.192
broadcast 213.235.253.207
gateway 213.235.253.193
up ip addr add 2001:1:1:1:0::2/64 dev eth0
up route -6 add default gw 2001:1:1:1:0::1
down ip addr del 22001:1:1:1:0::2/64 dev eth0
</code>

== See also ==
* [[Veth]]
* [[Differences between venet and veth]]

[[Category: Networking]]
[[Category: HOWTO]]

Virtual network device

2009-01-05T13:23:00Z

Sts: /* IPv6 */

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 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
</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
</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 venet you'll need to enable the following in your sysctl.conf:

<code>
net.ipv6.conf.default.forwarding = 1
net.ipv6.conf.all.forwarding = 1
</code>

In IPv6 you can't control forwarding per device, forwarding control has to take place in ip6tables, so all interfaces will forward IPv6 traffic.

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

You will as well need to configure a new v6 default gateway for your host:

<code>
ip addr add 2001:1:1:1:0::2/64 dev eth0
route -6 add default gw 2001:1:1:1:0::1
</code>

You can add these commands to your existing network configuration on Debian/Linux:

<code>
iface eth0 inet static
address 213.235.253.206
netmask 255.255.255.240
network 213.235.253.192
broadcast 213.235.253.207
gateway 213.235.253.193
up ip addr add 2001:1:1:1:0::2/64 dev eth0
up route -6 add default gw 2001:1:1:1:0::1
down ip addr del 22001:1:1:1:0::2/64 dev eth0
</code>

== See also ==
* [[Veth]]
* [[Differences between venet and veth]]

[[Category: Networking]]
[[Category: HOWTO]]

Virtual network device

2009-01-05T13:21:25Z

Sts: /* IPv6 */

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 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
</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
</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 venet you'll need to enable the following in your sysctl.conf:

<code>
net.ipv6.conf.default.forwarding = 1
net.ipv6.conf.all.forwarding = 1
</code>

In IPv6 you can't control forwarding per device, forwarding control has to take place in ip6tables, so all interfaces will forward IPv6 traffic.

If you enable IPv6 forwarding 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]] or [[http://mirrors.bieringer.de/Linux+IPv6-HOWTO/proc-sys-net-ipv6.html]]).

You will as well need to configure a new v6 default gateway for your host:

<code>
ip addr add 2001:1:1:1:0::2/64 dev eth0
route -6 add default gw 2001:1:1:1:0::1
</code>

You can add these commands to your existing network configuration on Debian/Linux:

<code>
iface eth0 inet static
address 213.235.253.206
netmask 255.255.255.240
network 213.235.253.192
broadcast 213.235.253.207
gateway 213.235.253.193
up ip addr add 2001:1:1:1:0::2/64 dev eth0
up route -6 add default gw 2001:1:1:1:0::1
down ip addr del 22001:1:1:1:0::2/64 dev eth0
</code>

== See also ==
* [[Veth]]
* [[Differences between venet and veth]]

[[Category: Networking]]
[[Category: HOWTO]]

Virtual network device

2009-01-05T12:35:37Z

Sts: