I’m working on replacing my FritzBox 7690 with a MikroTik hAP aX^2.
Since the FritzBox was provided by my service provider (A1 in Austria), I came a long way to make it work.
One of my last issues is as follows:
My MusicCast 20 (wireless speaker) was working fine when using the FritzBox. Since I’ve switched to MikroTik it won’t work anymore. More precisely: It won’t even connect to the router. All my other devices (laptop, phone, tablet) are working fine.
Do you have any firewall rules which would block (certain) internet connectivity for Yamaha?
In general there are two issues with WiFi connectivity of devices (which are too smart for their own good):
modern WiFi features which scare off older stations. Those include e.g. WPA-3, AX/BE features or even 40MHz channels on 2.4GHz band.
This doesn't seem to be the problem in your case though as Yamaha was able to pull DHCP lease.
"internet detect" ... or whatever it's called on a particular device. Devices try to access certain (hard-coded) services on internet (some could be considered as "calling home") and if they fail to do it, they declare connection "not working" and refuse any communication via such connection.
In your case this might be it. But troubleshooting of such problem is not trivial. Ideally one would sniff all traffic of such device (could be a bit harder to do on more "consumer friendly" router/APs which don't provide tools or hooks for that) and then compare it to traffic seen on "problematic" AP (your Mikrotik).
And then there's a third option:
LAN segmentation ... where device is put into one LAN segment (subnet) while controller is in another LAN subnet. Depending on particular connectivity modes it could either be that device rejects connectivity from "alien" subnets (security considerations) or that communication (or at least discovery) between controller and device is done via broadcast/multicast ... which are not routed (or can be routed but with additional setup in case of multicasts).
Major issue: you have assigned channel="channel_5GHz AC" channel-configuration to both wifi1 and wifi2. You have a list of hardcoded frequency and explicitly set band - so you'll only have 5ghz anyways. Using 5ghz-ac is a waste of capabilities on hap ax2. I don't know where these chains config comes from, maybe from Winbox.
Try disabling WPA3-PSK and let only WPA2-PSK. A lot of the so called “IoT” devices don’t get along to well with WPA3 standard.
Or, you can create a separate SSID for IoT devices (WPA2-PSK only) where you can move your MusicCast and let WPA3-PSK enabled on your main SSID where you connect your phones and PCs.
Today I was able to resolve the problem - and it is not direcly related to the MikroTik router:
When setting up the speaker by e.g. phone, you need to connect to its WiFi first to provide the details of the home-network. After that the speaker disconnects, logs onto the home-network and the app waits until the phone is reconnected to the home-network, for some data-transfer / verification I suppose. And that was the problem: My phone took too long and the app basically ran into a timeout.
The solution was to fiddle around with the phone and hope, that it reconnects to the original WiFi within the time the app provided.
Thanks,
Bear
P.S:
Hidden SSID did not make any difference. Still hidden.
WPA2 or 3 did not make any difference either. Still allowing both.
I have a very similar or even exact same issue. I’m trying to move the AP functionality from provider supplied device to a Mikrotik AC2.
I did not get one thing - why was your phone involved?
If the speaker worked with Fritz, it means it was already configured to join specific SSID. Mikrotik is broadcasting the same SSID, so the speaker configuration shouldn’t be necessary?