Virtual Ethernet device - Revision history

Apmuthu at 16:39, 2 October 2016

2016-10-02T16:39:20Z

Kir: Reverted edits by 192.240.191.2 (talk) to last revision by 194.190.52.93

2016-08-09T23:21:16Z

Reverted edits by 192.240.191.2 (talk) to last revision by 194.190.52.93

192.240.191.2 at 20:11, 9 August 2016

2016-08-09T20:11:43Z

192.240.191.2 at 20:10, 9 August 2016

2016-08-09T20:10:52Z

194.190.52.93 at 08:55, 15 January 2016

2016-01-15T08:55:27Z

Sergey Bronnikov: Marked this version for translation

2015-12-31T10:39:20Z

Marked this version for translation

Show changes

Sergey Bronnikov: add 'translate' tags

2015-12-31T10:38:51Z

add 'translate' tags

Apmuthu: /* External links */

2015-01-24T18:01:30Z

‎External links

Apmuthu: /* External links */

2015-01-24T17:48:20Z

‎External links

Apmuthu: /* External links */

2015-01-24T17:47:23Z

‎External links

@@ Line 370: / Line 370: @@
 * [http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/hints-daemons-radvd.html Linux IPv6 HOWTO, a chapter about radvd]
 * [http://sysadmin-ivanov.blogspot.com/2008/02/2-veth-with-2-bridges-on-openvz-at.html 2 veth with 2 bridges setup]
-* [http://forum.proxmox.com/archive/index.php/t-1733.html Non default gateway for CentOS OpenVZ container] - this applies to BlueOnyx in Proxmox as well. | [[Media:TwoGWsPVECentOS.pdf|Cache]]
+* [https://forum.proxmox.com/threads/physical-host-with-2-nics-each-with-different-gateways.1733/#post-9287 Non default gateway for CentOS OpenVZ container] - this applies to BlueOnyx in Proxmox as well. | [[Media:TwoGWsPVECentOS.pdf|Cache]]
 </translate>

@@ Line 16: / Line 16: @@
 === Kernel module === <!--T:4-->
-The <code>veth</code> module should be loaded. You can check it with the following commands.
+The <code>vzethdev</code> module should be loaded. You can check it with the following commands.
 <pre>
-# lsmod | grep veth
+# lsmod | grep vzeth
-veth                   13491  0
+vzethdev                8224  0
 </pre>
@@ Line 25: / Line 27: @@
 In case it is not loaded, load it:
 <pre>
-# modprobe veth
+# modprobe vzethdev
 </pre>

@@ Line 16: / Line 16: @@
 === Kernel module === <!--T:4-->
-The <code>vzethdev</code> module should be loaded. You can check it with the following commands.
+The <code>veth</code> module should be loaded. You can check it with the following commands.
 <pre>
 # lsmod | grep veth
@@ Line 25: / Line 25: @@
 In case it is not loaded, load it:
 <pre>
-# modprobe vzethdev
+# modprobe veth
 </pre>

@@ Line 18: / Line 18: @@
 The <code>vzethdev</code> module should be loaded. You can check it with the following commands.
 <pre>
-# lsmod | grep vzeth
+# lsmod | grep veth
-vzethdev                8224  0
+veth                   13491  0
 </pre>

@@ Line 318: / Line 318: @@
          gateway 192.168.1.254
 </pre>
-Follow the steps below for making a veth bridge persistent with the included script. That will automatically add each container to the bridge when it is started. Finally, specify vzbr0 as the bridge when adding the network interface to a container, as describe above. No configuration is needed on [[CT0]] for forwarding packets, proxy arp or additional routes. The interface in each [[CT]] can be configured as desired. Everything "just works" according to normal network interface configuration and default routing rules. Note that as discussed in the troubleshooting section below, bridged packets by default pass through the FORWARD iptables chain. Take care when adding rules to that table that bridged packets are not mistakenly blocked. This behavior can be disabled, if desired.
+Follow the steps below for making a veth bridge persistent with the included script. That will automatically add each container to the bridge when it is started. Finally, specify vzbr0 as the bridge when adding the network interface to a container, as describe above. No configuration is needed on [[CT0]] for forwarding packets, proxy arp or additional routes. The interface in each [[CT]] can be configured as desired. Everything "just works" according to normal network interface configuration and default routing rules. Note that as discussed in the troubleshooting section below, bridged packets by default pass through the FORWARD iptables chain. Take care when adding rules to that table that bridged packets are not mistakenly blocked. This behavior can be disabled, if desired (sysctl: <code>net.bridge.bridge-nf-call-iptables</code>).
 === Making a veth-device persistent === <!--T:77-->

@@ Line 1: / Line 1: @@
 '''Virtual Ethernet device''' is an Ethernet-like device that can be used
 inside a [[container]]. Unlike a [[venet]] network device, a [[veth]] device
@@ Line 310: / Line 311: @@
 * [http://sysadmin-ivanov.blogspot.com/2008/02/2-veth-with-2-bridges-on-openvz-at.html 2 veth with 2 bridges setup]
 * [http://forum.proxmox.com/archive/index.php/t-1733.html Non default gateway for CentOS OpenVZ container] - this applies to BlueOnyx in Proxmox as well. | [[Media:TwoGWsPVECentOS.pdf|Cache]]
 [[Category: Networking]]
 [[Category: HOWTO]]