Hey All, TL;DR: traffic leaving a bridge over a vlan does not get tagged but leaves untagged after upgrade. Is this by design?
Longer version: Lost most of my night trying to figure out why my setup ended up breaking. I found a solution but I am not exactly happy with it. I think this breakage may have been intended. However I am not sure, there were a couple of vlan-tagging fixes/changes between 5.5 and 5.6. My setup (worked fine from 5.4 -> 5.5): trunk0 (LACP+tagged vlans) = em0, em1, em2 vlan150, vlan200 and vlan300 over trunk0 tun0, tun1, tun2 and tun3 = OpenVPN vether0 = for ip/dhcp bridge0 = vlan150, vether0, tun0-tun3 Every worked fine on 5.4 and 5.5. Everything on the bridge was talking to each other including physical devices behind vlan150. After upgrading to 5.6 everything going over the bridge was fine except devices behind vlan150. After a lot of head scratching I noticed that traffic coming from the bridge did not get tagged with vlan id 150 but came out untagged. In the end worked around the issue by removing em0 from trunk0 and reconfiguring it on the switch to work as an access port. I swapped out vlan150 for em0 on the bridge and everything was working again. Not very happy with this work around but it will do for now. Anybody else experiencing this? Did it get broken by design? (AKA was I doing something stupid the last year? -- probably the case) Regards Jorge (sleepy sysadmin)
