Slow Hex file transfer speed

As pointed out by @anav, you are giving the hEX mixed messages about whether vlan 10 should be tagged or untagged. ROS assumes you know what your are doing, and provides very little hand holding in the configuration, it won’t even generate warnings sometimes. And his advice should work as long as you do want ether5 to use tagged frames on the wire to/from the WAP for vlan 10.

The bridge base device would normally have pvid 1 when it is not specified, and untagged traffic it receives from the switch ASIC will be delivered to the bridge interface. Since you don’t have any ip address associated with the bridge device, and you do have an /interface vlan for vlan 10, traffic received from the switch ASIC with vlan 10 tag would normally be delivered to the interface you named main-vlan, but because you also set the pvid to 10 on ether5 (but are blocking untagged frames) I am not sure exactly what it is doing. If it is working except for not getting the performance you were expecting, I can only guess that it is sending tagged frames for vlan 10 out of ether5. Even though the pvid is set to 10 on ether5, and if would normally then send traffic out ether5 untagged for vlan 10, since you explicitly told it to use tagged on ether5 in the / following the normal rule of untagging the traffic egressing for a vlan that matches the pvid of the port.

So, start by verifying what you expect traffic for vlan 10 to be handled on ether5. Does the WAP expect tagged traffic for vlan 10, or untagged traffic for vlan 10?

And if you are going to create a vlan interface for vlan 10 (i.e. main-vlan), then you should not use the same vlan as the pvid on the bridge. If you are not going to use an ip address on the bridge device, just make sure that the vlan associated with the bridge device isn’t used elsewhere. You can leave it at one, or you could specify a high vlan that isn’t going to be used anywhere, e.g. like 4094 or some other high vlan that you don’t plan to use anywhere else. Or better also set the bridge to accept only tragged frames, then nothing will leak through to the base bridge interface input even if an ip address was there.
Bridge PVID and frame type.png
In the following the highlighted things in same color are the “contradictory instructions” you are giving the hEX.

/interface bridge
add admin-mac= auto-mac=no comment=defconf name=bridge pvid=10 vlan-filtering=yes
/interface vlan
add interface=bridge name=main-vlan vlan-id=10
/interface bridge port
add bridge=bridge comment=defconf frame-types=admit-only-vlan-tagged interface=ether5 pvid=10
/interface bridge vlan
add bridge=bridge comment=main-vlan **tagged=**bridge,ether5 untagged=ether2,ether3,ether4 vlan-ids=10