Hi,
I am using two hAP ax2 and one hAP ax3 to cover my home with Wifi.
All devices are managed via CAPsMAN, which first was running in the ax3, but now - after some weird testing - is running on an hEX S.
Finally all devices are connected via layer2 switch (TP-LINK).
What happens? If a mobile device (Android based smartphones or a chromebook) is connected with a hAP ax2 and the connection is lost, by turning of wlan for example, and the connection is established again in reach of hap ax3 radio, the wlan is connected but no communication is possible except pinging the router itself.
After some time with reconnecting again communication is possible as expected.
I startet my journey on 7.14.2 with container and all stuff on the ax3. I did a reset and uninstall of the container package. I recovered in cap mode. Ended with 7.15beta on the ax3. Tried out configuration without CAPsMAN (same SSID and security) Same Behavior. Nothing did the job.
Switching from ax3 to ax2 or ax2 to ax2 works fine.
I am pretty new in the Mikrotik-Universe. Can anyone help?
The way you explain the symptoms, the problem might be also in ARP entry aging on switches/bridges … all mentioned devices are part of it, including the TP-link switch. If you can, connect both hAPs to hEX directly just to make sure that TP-link isn’t playing games.
I changed the cables. Now the hEX is directly connected with the ax3 and both ax2 are directly connected with ax3. Not exactly what you suggested, but the switch is no more in the game.
Unfortunately the problem is still alive. In my tests before I already inspected the ARP-table of the ax3 and in Winbox I detected an immediate shift from ether1 to wifi1. No double entries or missing entry.
This is really weird. In your opening post you wrote that wireless client can ping gateway (router), but the rest of (internet?) traffic is blocked for a while. But if device wants to communicate with internet, it is sending traffic to router … and that works as you are saying.
You can try to torch traffic and see if traffic patterns for the “roaming” client show anything …