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 ? Mayve try to configure vlan1 to disable vlan filtering ? 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) 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) ----- 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
