My query is to those who have a hAP ax^2 and have tried to bridge all ports.
Non-working configuration was:
Flags: X - DISABLED, I - INACTIVE
Columns: INTERFACE, BRIDGE, HW, PVID, PRIORITY, PATH-COST, INTERNAL-PATH-COST, HORIZON
# INTERFACE BRIDGE HW PVID PRIORITY PATH-COST INTERNAL-PATH-COST HORIZON
0 ether2 bridge yes 31 0x80 10 10 none
1 I ether3 bridge yes 1 0x80 10 10 none
2 ether4 bridge yes 1 0x80 10 10 none
3 ether5 bridge yes 1 0x80 10 10 none
4 ether1 bridge yes 32 0x80 10 10 none
Whereas working configuration is:
Flags: X - DISABLED, I - INACTIVE
Columns: INTERFACE, BRIDGE, HW, PVID, PRIORITY, PATH-COST, INTERNAL-PATH-COST, HORIZON
# INTERFACE BRIDGE HW PVID PRIORITY PATH-COST INTERNAL-PATH-COST HORIZON
0 ether1 bridge yes 32 0x80 10 10 none
1 ether2 bridge yes 31 0x80 10 10 none
2 I ether3 bridge yes 1 0x80 10 10 none
3 ether4 bridge yes 1 0x80 10 10 none
4 ether5 bridge yes 1 0x80 10 10 none
All my other configuration - bridging, IP routing, firewalling, Internet access etc are working. They are configured on VLANs over the bridge so aren't directly related to the bridge ports.
I could see packets tagged with VLAN 32 on the bridge (using /tool/sniffer), but they weren't seen on ether1 - like it wasn't part of the bridge. I'd seen that previously when bringing a port out of disabled state, although that was resolved with a reboot. On this occasion however, that didn't work.
The change that made the difference was the ordering. Hence the question whether others had observed the same behaviour.