I will try that. There are many places with no overlap (long corridor) and that I would not make worse.
Aruba or better said HP is in a different league. I mostly have just small installations of up to 10 AP
I’m going to take a closer look at Ubiquiti combined with Mikrotik (Hotspot, VLAN). Can Ubiquiti seamless roaming wireless use WITHOUT UniFi Controller (UniFi controller only for configuration)? I know is not a UBNT forum but I will certainly not be the only one looking for an alternative for Indoor WLAN.
i suggest you to take a tour in ubiquiti forums before buying, some time ago i read about some issues about this topic, better check that issues has been solved before buying
Dear angboontiong, why you suggest Aruba and not Mikrotik?
Wich is your experience?
I’m searching some experience with medium large installations with mikrotik and capsman indoor.
In my own experience (got several RBs in my home) if you set them up with CAPsMANv2 (wireless-cm2) and set all of them to the same frequency/ssid/key (just the exact same provisioning profile), the devices freely roam on their own (my iPhone very quickly swaps access points when I move through my home, within 30 seconds of being moved).
They key here is the APs must be on the same channel (it did not work with different channels)
I think it does depend on the Wi-Fi client hardware you are using.
However it does make sense only same-channel roaming works seamless:
To check for APs on different channels it would have to go switch channels, do a scan, which would or might interrupt your connectivity for most devices (i.e. those that can’t be on two independant channels at once)
If channel is same, it can observe beacon frames without having to swap channels at all and judge signal strength to swap over
I don’t know if CAPsMAN is required to make this possible (I don’t know if it syncs the WPA2 Wi-Fi unicast keys or group keys or not). But this is controlled by the client devices, not the APs.
So if your client device does not do it, then it doesn’t (it might depend on driver, firmware and OS since all of those could initiate such swapping behaviour)