Sorry for the extremely late reply but I have been working on other projects.<div><br></div><div>I am sure it was configured correctly. But here is the configuration.</div><div><br></div><div>The switch PVID of the both eth0 and eth1 is vlan 2 and there is vlan 3, 4, 5 traffic on bond0. The bond0 interface works as long as another virtual machine does not specify a vlan 2 tag on their virtual network interface. As soon that that machine is started the bond0 ip stops responding. </div>
<div><br></div><div><div># network interface settings</div><div>auto lo</div><div>iface lo inet loopback</div><div><br></div><div>iface eth0 inet manual</div><div><br></div><div>iface eth1 inet manual</div><div><br></div>
<div>auto bond0</div><div>iface bond0 inet manual</div><div> slaves eth0 eth1</div><div> bond_miimon 100</div><div> bond_mode 802.3ad</div><div><br></div><div>auto vmbr0</div><div>iface vmbr0 inet manual</div>
<div> address 192.168.254.5</div><div> netmask 255.255.255.0</div><div> gateway 192.168.254.1</div><div> bridge_ports bond0</div><div> bridge_stp off</div><div> bridge_fd 0</div></div>
<div><br></div><div>A way around this problem was to set PVID 1 on the switch and move the ip to vmbr0v2 with this config. This allowed me to use vlan tagging on all virtual machines while maintaining the ip address in vlan 2. However this had the draw back of not allowing tagged frames to work on vmbr0 any longer which would not allow trunking to a virtual machine.</div>
<div><br></div><div><div># network interface settings</div><div>auto lo</div><div>iface lo inet loopback</div><div><br></div><div>iface eth0 inet manual</div><div><br></div><div>iface eth1 inet manual</div><div><br></div>
<div>auto bond0</div><div>iface bond0 inet manual</div><div> slaves eth0 eth1</div><div> bond_miimon 100</div><div> bond_mode 802.3ad</div><div><br></div><div>auto vmbr0</div><div>iface vmbr0 inet manual</div>
<div> bridge_ports bond0</div><div> bridge_stp off</div><div> bridge_fd 0</div><div><br></div><div>iface bond0.2 inet manual</div><div> vlan_raw_device bond0</div><div><br></div><div>auto vmbr0v2</div>
<div>iface vmbr0v2 inet static</div><div> address 192.168.254.5</div><div> netmask 255.255.255.0</div><div> gateway 192.168.254.1</div><div> bridge_ports bond0.2</div><div> bridge_stp off</div>
<div> bridge_fd 0</div></div><div><br></div><div>The follow configuration is what works with my patch and allows vmbr0 to pass tagged frames to a virtual machine and also allow vlan specified interfaces in proxmox.</div>
<div><br></div><div><div># network interface settings</div><div>auto lo</div><div>iface lo inet loopback</div><div><br></div><div>iface eth0 inet manual</div><div><br></div><div>iface eth1 inet manual</div><div><br></div>
<div>auto bond0</div><div>iface bond0 inet manual</div><div> slaves eth0 eth1</div><div> bond_miimon 100</div><div> bond_mode 802.3ad</div><div><br></div><div>auto vmbr0</div><div>iface vmbr0 inet manual</div>
<div> bridge_ports bond0</div><div> bridge_stp off</div><div> bridge_fd 0</div><div><br></div><div>auto vmbr0.2</div><div>iface vmbr0.2 inet manual</div><div> vlan_raw_device vmbr0</div><div><br>
</div><div>auto vmbr0v2</div><div>iface vmbr0v2 inet static</div><div> address 192.168.254.5</div><div> netmask 255.255.255.0</div><div> gateway 192.168.254.1</div><div> bridge_ports vmbr0.2</div>
<div> bridge_stp off</div><div> bridge_fd 0</div></div><div><br></div><div><br></div><div>The patch just changes the way the vlan bridges are created.</div><div><br></div><div>If you have more questions feel free to let me know. One other advantage that may come of this is firewalling between virtual machines. As you could do firewalling in a virtual appliance instead of at the host level using only Shorewall. This configuration would allow firewalling/routing between the bridges.</div>
<div><br></div><div><br><div class="gmail_quote">On Tue, Jul 10, 2012 at 12:58 AM, Dietmar Maurer <span dir="ltr"><<a href="mailto:dietmar@proxmox.com" target="_blank">dietmar@proxmox.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">> I have been posting information to this forum thread in regard to a<br>
> problem/patch for the network bridge configuration.<br>
> <a href="http://forum.proxmox.com/threads/10110-New-network-configuration-" target="_blank">http://forum.proxmox.com/threads/10110-New-network-configuration-</a><br>
> with-bridge-vlan-interfaces<br>
><br>
> Basically the problem with the existing configuration is if you want to utilize<br>
> the vmbr0 interface as a management interface or a tagged vlan trunk to a<br>
> virtual machine it stops working as soon as you start a virtual machine using<br>
> a vlan tag. This is because when bringing the respective vlan bridge online it<br>
> is bridging to the underlying physical interface's vlan sub interface (ex,<br>
> eth0.2, bond0.3). This causes the existing bridge root interface to stop<br>
> working. I verified this with tcpdump on vmbr0.<br>
<br>
</div>Maybe you simply configure it the wrong way? (send your config please)<br>
<span class="HOEnZb"><font color="#888888"><br>
- Dietmar<br>
<br>
</font></span></blockquote></div><br></div>