Difference between revisions of "Talk:Virtual Ethernet device"
m (→Answer: Multiple persistent Veth interfaces) |
(→Multiple persistent Veth interfaces) |
||
| Line 16: | Line 16: | ||
The script for making a persistent bridge get added to a particular host-bridge on startup VPS/VE, doesn't seem to account for having multiple bridges. I have a bridge to a private lan for administrative functions and a bridge to the public network for inbound connections for services. How might one ensure that the vethVEID.x's are hooked up to the bridges on the host every time the VE is started? --[[User:Btrotter|Btrotter]] 05:34, 17 March 2008 (EDT) | The script for making a persistent bridge get added to a particular host-bridge on startup VPS/VE, doesn't seem to account for having multiple bridges. I have a bridge to a private lan for administrative functions and a bridge to the public network for inbound connections for services. How might one ensure that the vethVEID.x's are hooked up to the bridges on the host every time the VE is started? --[[User:Btrotter|Btrotter]] 05:34, 17 March 2008 (EDT) | ||
| − | : Please take a look on articles [http://wiki.openvz.org/Using_private_IPs_for_Hardware_Nodes Using private IPs for Hardware Nodes] and [http://vireso.blogspot.com/2008/02/2-veth-with-2-brindges-on-openvz-at.html Bridged Networks for OpenVZ]. There you will find scripts which will help you to manage 2 bridges, and you can simply extend this script to use more then 2 bridges. --[[User:Major|Major]] | + | : Please take a look on articles [http://wiki.openvz.org/Using_private_IPs_for_Hardware_Nodes Using private IPs for Hardware Nodes] and [http://vireso.blogspot.com/2008/02/2-veth-with-2-brindges-on-openvz-at.html Bridged Networks for OpenVZ]. There you will find scripts which will help you to manage 2 bridges, and you can simply extend this script to use more then 2 bridges. --[[User:Major|Major]] 15:59, 27 March 2008 (MSK) |
Revision as of 12:58, 27 March 2008
Under Common Configurations -> Simple configuration -> Configure devices in VE0, the example shows
[host-node]# echo 1 > /proc/sys/net/ipv4/conf/eth0/forwarding [host-node]# echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp
being run on the host node, VE0. I don't think this can be correct, because eth0 exists in VE 101, not VE0. -- —The preceding unsigned comment was added by Andrex (talk • contribs) .
- This is correct, because we need to enable forwarding on both network interfaces in VE0 (host-node eth0 and veth101.0) to allow the network packets on one network interface (host-node eth0) to be forwarded to another network interface (veth101.0). The same thing with proxy ARP, we need to enable it on host-node eth0 and veth101.0 network interfaces. --Major 08:42, 17 July 2006 (EDT)
Multiple persistent Veth interfaces
The script for making a persistent bridge get added to a particular host-bridge on startup VPS/VE, doesn't seem to account for having multiple bridges. I have a bridge to a private lan for administrative functions and a bridge to the public network for inbound connections for services. How might one ensure that the vethVEID.x's are hooked up to the bridges on the host every time the VE is started? --Btrotter 05:34, 17 March 2008 (EDT)
- Please take a look on articles Using private IPs for Hardware Nodes and Bridged Networks for OpenVZ. There you will find scripts which will help you to manage 2 bridges, and you can simply extend this script to use more then 2 bridges. --Major 15:59, 27 March 2008 (MSK)
