Today I've been fighting with my #mikrotik hap ax³ in order to enable the 2.4 GHz WiFi.
Spent a couple of hours to identify why doesn't my legacy device see the SSID, I changed encryption and all the possible network settings, I read the documentation on frequencies and compared the channel tables trying to understand if my US device should work in Japan at all. And nothing.
I ended up with the finding that even the "Scan" button on the 2 GHz interface can't find any networks. No issues were reported to logs so I've updated packages, firmware, rechecked all the settings. Still nothing.
At last I stumbled upon the post https://forum.mikrotik.com/viewtopic.php?p=1102060#p1102060
And… It helped! All I had to do is to power-cycle the device! And yet no log messages, no errors, no nothing, but it just started working.
Hey, @mikrotik! I suggest adding something like "turn it off and on again. No, seriously!" into the troubleshooting section in your Confluence, this might have saved many hours of debug
=> More informations about this toot | More toots from rayslava@lor.sh
@rayslava there is never a reason to power cycle a device that is not shown to the user, certainly not related to wifi. Config is applied immediately. It could have been some other problem that the power cycle resolved
=> More informations about this toot | More toots from mikrotik@mikrotik.social
@mikrotik and I could even agree if I didn't find several posts on your forum with the same issue solved the same way.
There is nothing wrong, nothing in logs, it just looks like the 2.4 GHz hw is placed into the deep space and can find nothing around: scan results are empty, frequency usage is zero.
That might even be not a mikrotik fault: looking at the symptoms I can suggest that this is related to wireless interface firmware.
=> More informations about this toot | More toots from rayslava@lor.sh
text/geminiThis content has been proxied by September (3851b).