Compatibility
Due to storage, RAM, and architecture requirements, only the following products can replace their bundled wireless software package with wifiwave2:

hAP ac³ (non-LTE)
Audience and Audience LTE6 kit
RB4011iGS+5HacQ2HnD*
* The 2.4GHz wireless interface on the RB4011iGS+5HacQ2HnD is not compatible with the wifiwave2 package. It will not be usable with the package installed.

It is also possible to install the WifiWave2 package on other devices to use WifiWave2 CAPsMAN: builds for x86, ppc, mmips and tile architectures contain the configuration utilities needed to centrally manage interfaces (as a CAPsMAN controller). Builds for arm and arm64 also contain interface drivers and firmware.

Compatibility
The wifi-qcom-ac package includes alternative drivers for IPQ4018/4019 and QCA9984 radios that make them compatible with the WiFi configuration menu.

As a rule of thumb, the package is compatible with 802.11ac producs, which have an ARM CPU. It is NOT copmatible with any of our 802.11ac products which have a MIPS CPU.

Compatible Audience, Audience LTE kit, Chateau (all variants of D53), hAP ac^2, hAP ac^3, cAP ac, cAP XL ac, LDF 5 ac, LHG XL 5 ac, LHG XL 52 ac, NetMetal ac^2, mANTBox 52 15s, wAP ac (RBwAPG-5HacD2HnD), SXTsq 5 ac

Incompatbile RB4011iGS+5HacQ2HnD-IN (no support for the 2.4GHz interface), Cube 60Pro ac (no support for 60GHz interface), wAP ac (RBwAPG-5HacT2HnD) and all other devices with a MIPSBE CPU

I read that wifiwawe2 is implementing 802.11r/k/v that can solve this problem

• 802.11r accelerates re-authentication when roaming, i.e. this is mostly helpful when you are using EAP authentication. PSK authentication is already fast without it.
• 802.11k provides a list of alternative APs to the client, i.e. it accelerated the search for stronger APs once your signal becomes weak.
• 802.11v enabled the AP to make roaming suggestions to the client, e.g. this allows the AP to tell the client to prefer 5g over 2g. But most modern clients prefer 5g anyway.

Guess they need to update the page...