This:For the other way you need tagged vlan also on bridge interface, i.e. tagged=ether2,br.
/interface bridge vlan add bridge=br tagged=ether2,br untagged=ether1-wan vlan-ids=10
we will work on this problem but first we need to finetune the new wireless driver for the new hardware and then we would try to implement the fix for the old wireless hardware.
Only one?wireless engineer is working
Nope, pls check viewtopic.php?f=2&t=132576So, it is a LAN-WAN routing issue. Can I confirm with all on here who have posted data across the WAN interface: