[pve-devel] [PATCH] support QinQ / vlan stacking

Alexandre DERUMIER aderumier at odiso.com
Fri Mar 13 08:21:18 CET 2015


>>So it should be safe to use the vlan_filtering code?

Maybe can we wait for rhel 7.1 kernel ? I think it should be pretty stable, but it need to be tested.

----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "Stefan Priebe" <s.priebe at profihost.ag>, "aderumier" <aderumier at odiso.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Jeudi 12 Mars 2015 15:52:06
Objet: Re: [pve-devel] [PATCH] support QinQ / vlan stacking

> Am 12.03.2015 um 09:55 schrieb Alexandre DERUMIER: 
> >>> Strangely QinQ works fine with vanilla 3.10 and also with RHEL 3.10. No 
> >>> idea what has changed. 
> > 
> > Yes, but the vlan_filtering qinq patch from 3.16 is about managing all 
> > inside the linux bridge. 
> > (without tagging on ethX interfaces). 
> > 
> > and, linux bridge is aware of vlan tags and qinq tags with this. 
> 
> ah OK but this also means we rely on kernel version and features. I 
> would still vote just for your ebtables patches. You can control all 
> packet types also VLAN packets with it and it works since Kernel 3.2. 

Our jessie release will be based on 3.10.0, and we will not support older 
versions. 
So it should be safe to use the vlan_filtering code? 

And we can also apply the ebtables patch. Or is there something preventing this? 




More information about the pve-devel mailing list