We have found you need to nest the bridges to get QinQ to work in all
scenarios.
e.g. The above patch will work for MOST scenarios, but if you attach a vlan
aware VM to the parent vmbr0 bridge it will cause traffic to the VM's to
stop, or will not be able to see the tagged frames.
The patch we use only has one other minor change:
- activate_bridge_vlan_slave($bridgevlan, $iface, $tag);
+ activate_bridge_vlan_slave($bridgevlan, $bridge, $tag);
On Sat, Feb 14, 2015 at 9:41 PM, Stefan Priebe <s.pri...@profihost.ag>
wrote:
>
> Signed-off-by: Stefan Priebe <s.pri...@profihost.ag>
> ---
> data/PVE/Network.pm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/data/PVE/Network.pm b/data/PVE/Network.pm
> index 00639f6..97f4033 100644
> --- a/data/PVE/Network.pm
> +++ b/data/PVE/Network.pm
> @@ -323,7 +323,7 @@ sub activate_bridge_vlan {
>
> my @ifaces = ();
> my $dir = "/sys/class/net/$bridge/brif";
> - PVE::Tools::dir_glob_foreach($dir, '((eth|bond)\d+)', sub {
> + PVE::Tools::dir_glob_foreach($dir, '((eth|bond)\d+(\.\d+)?)', sub {
> push @ifaces, $_[0];
> });
>
> --
> 1.7.10.4
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
