>>The relevant commit says it's disabled by default. Strangely i don't see >>how to enable and use this from the commits message. yed, I see that too.
also found this: "Bridge VLAN kernel/iproute2 incompatibility" http://www.spinics.net/lists/linux-ethernet-bridging/msg04942.html don't known if if could be related? a kernel patch has been submit in august. >> Mayve try to configure vlan1 to disable vlan filtering ? >>What do you mean by that? some hardware see vlan1=novlan, but not sure it's working like that >>mhm i could try that. So you mean instead of adding: >>vmbr1.3021@vmbr1 >>and >>vmbr1v3021 >> >>just use vmbr1.3021@vmbr1 and add the tap device to that one? mmm, what is vmbr1.3021@vmbr1? current proxmox implementation is ethx.302---vmbr1v302 (can you do a brctl show?) But, with new vlan code, what we will do should be ethx----vmbr1----tap and configure virtual port on vmbr1, where tap is plugged, with vlan tag 302. (like a real switch) ----- Mail original ----- De: "Stefan Priebe" <s.pri...@profihost.ag> À: "Alexandre DERUMIER" <aderum...@odiso.com> Cc: pve-devel@pve.proxmox.com Envoyé: Jeudi 29 Août 2013 20:58:04 Objet: Re: [pve-devel] playing with 3.10 Am 29.08.2013 20:52, schrieb Alexandre DERUMIER: > Hi Stefan, > > I don't have a look a vlan-bridge implementation in new kernel. > > As far I known, bridge support now vlan tagging (by port?). Maybe it's > tagging by default ? The relevant commit says it's disabled by default. Strangely i don't see how to enable and use this from the commits message. > Mayve try to configure vlan1 to disable vlan filtering ? What do you mean by that? > Or maybe can we try to implement new vlan code ? > (don't tag anymore on eth with multibridge, but use only 1 bridge with > tagging port) mhm i could try that. So you mean instead of adding: vmbr1.3021@vmbr1 and vmbr1v3021 just use vmbr1.3021@vmbr1 and add the tap device to that one? > I really don't known how it's work, I'll try to have a look at it next week. > (I think rhel7 kernel will use it, so it should come next year with openvz > for proxmox) Yes it will use that one. Stefan > > ----- Mail original ----- > > De: "Stefan Priebe - Profihost AG" <s.pri...@profihost.ag> > À: pve-devel@pve.proxmox.com > Envoyé: Jeudi 29 Août 2013 16:02:12 > Objet: [pve-devel] playing with 3.10 > > Hi, > > as Linux Kernel 3.10 ist the newest long term kernel i'll start > migrating all my machines to it. > > Everything works fine except for tap devices with VLANs on top of bridges. > > I'm pretty sure that this i related to this commit: > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=93197b > > > Has any body an idea how to get it working again for proxmox? I already > tried to compile the kernel with or without BRIDGE_VLAN_FILTERING but it > doesn't make a difference. VLAN packages never passes the bond to bridge > to the tap device. > > Greets, > Stefan > _______________________________________________ > 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
