I think email is probably the best method. If we pool efforts with a clear description of what we need and get requests in via email so it’s know how wide the impact is, we have the best chance probably of getting their attention. Some older posts:
http://forum.mikrotik.com/t/rb2011-how-do-i-strip-tagged-vlan-0/94770/1
http://forum.mikrotik.com/t/switch-chip-fun-vlan-0-issue/58029/1
http://forum.mikrotik.com/t/vlan-0-and-802-1p-tag/69446/1
http://forum.mikrotik.com/t/is-native-vlan0-or-vlan1-confused/135472/1
http://forum.mikrotik.com/t/802-1x-dot1x-client-not-working-when-interface-is-on-a-bridge/131984/1
Why MikroTik chooses to ignore packets that are priority tagged (but no VLAN, hence VLAN ends up being 0x000) is the root of the cause I believe. There are the following situations that can work:
- If both the 802.1x and TCP traffic function with the 802.1Q only containing a 802.1P priority tag, everything would be simple and ideal (no bridge). Traffic would be treated as if not tagged by a VLAN with 802.1Q.
- If attached to a bridge with VLAN filtering, allowing 802.1x to function (which is currently broken)
- If attached to a bridge without VLAN filtering, it should allow traffic (similar to #1, both situations would allow for VLAN 0 traffic to be treated as non-tagged in terms of 802.1Q VLANs)