Hi,
I have purchased hAP AX3 and CAP AX for my home wireless network but it has issues with connection of mobile devices (android and ios).
Currently, I have all the default settings on both units except for cAP AX. On cAP AX I only changed a subnet in Quick settings menu from 192.168.88.xxx to 192.168.89.xxx. The reason I have done this is that it did not receive any internet from hAP unit when I plugged a cable either to ETH1 (wan) or ETH2 (lan), but when I changed the subnet to above parameters it gets an internet when cable from hAP unit is connected to LAN port
The issue is that a mobile device has “no internet” when I connect to one of the units (i.e. cAP) and then reconnect to another (i.e. hAP) and I need to reset a network settings and reboot the phone in order to connect to hAP unit, however when I try to connect after hAP to cAP unit again i get the same “no internet” error. On my windows laptop I do not have any issues.
The strange thing I’ve noticed is that when I connect to cAP unit, I can see that device in DHCP Leases on hAP unit, but when I connect to hAP unit, I see that devices in dhcp leases on cAP unit. Is that normal? However, I would gladly arrange a cAP as an AP and process all the traffic through hAP unit, but do not know how to do that properly, because when I just turn off DHCP server, it does not even connect to cAP unit at all…
P.S. I have configured RB4011 unit with 6 cAP AC using CAPsMAN in my minihotel and it does not have any issues like above and it works like charm that’s why I decided to replace all my asuses\tp-links to mikrotik
Would be appreciate for any help
Is it WiFi package or the new one WiFi2 installed? Do you have WPA3 enabled?
@anav created very useful topic if you don’t know how to setup cAP as AP
https://forum.mikrotik.com/viewtopic.php?t=182276
Start from here and then post if you get stuck 
Yes, I have updated both RouterBoard and WiFi2 updated on both devices (ver.7.10.1). I will dig into WPA3 auth because I rememeber I had some issues with that too on another devices. Thank you.
Will also check the thread which gigabyte091 proposed, maybe I will switch CAP AX to AP mode
UPDATED: I have removed WPA3 PSK (only WPA2 PSK left) and now it works with no issues. Dunno why, but I remember I had the same issue with non-mikrotik routers too
As I reported in other thread … Ruckus Unleashed networks I operate do have same problem with WPA3 … some devices … not only mobile … do not connect.
Try 7.11beta2 and then enable WPA2/3, for me 7.11beta2 is the best yet regarding wireless performance.
Thanks! Yes, the only way to turn the cAP into AP is to turn off the DHCP server (it’s obvious even for me, cuz I am noob in all that networks things 
) and that was the first thing I did when I plugged in the cAP AX… However I did that in Quick set menu and it did not work at all… Now, I’ve checked your link and did that manually and it finally turned into un-routed AP. I confirm that Quick set menu is total EVIL
Thank you
I have one more question to not to create another thread: I want to create a seamless network using these to hAP and cAP units. Can I achieve that just naming networks on both devices with identycal names (separately for 2,4ghz and 5ghz, of course)? Or I need to configure CAPsMAN?
I never used Quick set menu, that was one of the first advices i get on this forum 
Yes, for roaming you need to configure CAPsMAN.
Wifi wave2 provides some support for faster roaming (802.11r), but devices will also roam without the use of CAPsMAN.
How did you achieved that ?
This is from Mikrotik help page:
Properties related to 802.11r fast BSS transition only apply to interfaces in AP mode. Wifiwave2 interfaces in station mode do not support 802.11r.
For a client device to successfully roam between 2 APs, the APs need to be managed by the same instance of RouterOS. For information on how to centrally manage multiple APs, see CAPsMAN
Station mode is when being connected to another wifi network.
2 radio interfaces (5GHz and 2.4GHz) on the same devices, are also managed by the same ROS instance. So “roaming” will work there too (read: moving from 2.4GHz channels to 5GHz and vice versa).
Capsman allows you to extend that behavior across devices.
Yea, for 2.4 and 5 GHz on the same device i understand that but topic autor is mentioning, if i understand correctly, roaming between hAP and cAP and for that he needs CAPsMAN because those are two different devices.
But then, is it possible for CAPsMAN to control local interfaces ?
As far as I know, no. You would need to configure those locally (with 90-95% same settings as for capsman).
But … since capsman controller AND the local interfaces are on the same device, it would still be under control of the same ROS instance.
And enabled FT ? So this works without capsman on multiple APs ?
Not entirely.
Multiple APs without capsman = not the same ROS instance = no roaming under ROS implementation of 802.11r fast BSS transition.
Clients will move from AP to AP (and access lists may help to kick them out sooner) but it will take longer.
Yea, and that was the only reason I use CAPsMAN, proper roaming.
For two APs CAPsMAN is overkill but it enables roam between APs… Now the only problem that remains is multiple VLANs, without workarounds…