You are right, wlan1, wlan1 work fine now.
As for WinBox and ether5, although it should be able to work with MAC only it doesn’t!
It auto replaces it (in “Connect to:”) with IP4 (0.0.0.0) and connection fails. It works with IP6 though.
I think this started today, where there are 2 “neighbors” to select from, one has IP4 (valid for all other ports and 0.0.0.0 for ether5) and the other IP6 for each port.
The MAC address column always contains ether5 MAC, no matter the port.
I’ll check out the effects of “frame-types=admit-only-untagged-and-priority-tagged” setting.
Anyway it works now, thanks again!
Mac Winbox connection sometimes Is “strange” I have seen something like you describe in the Winbox VM in GNS3, but not always, It may depend on the IP4 coming out as 0.0.0.0, but I am not really sure, It could be connected to the APIPA address you are getting (169.254.x.y).
Just assign a static IP address (say) 192.168.89.1/30 to ether5 and set your PC (temporarily) to the manual/static 192.168.89.2 255.255.255.252, so that you can surely connect to ether5.
It remains to understand how exactly the current “bridge” settings should be translated to “switch” ones and if It Is actually worth the time/hassle.
It Is not at all clear to me, CGGXANNX Is the expert on the matter and he promised to make some tests on a hap ac2, so keep an eye on this thread:
http://forum.mikrotik.com/t/hex-poe-bridge-mode-is-only-a-switch/182489/10