Something puzzles me about wpad versions when it comes to 802.11k. (In my case I am referring to the difference between wpad-basic-mdebtls & wpad-mbedtls given that I use WPA3/sae encryption.)
With wpad-basic[-mbedtls], enabling 802.11k in the /etc/config/wireless file and using openwrt-rrm-nr-distributor to ensure neighborhood reports are populated seems to do the job. However, 802.11k settings are not exposed within the luci admin interface.
Switch to wpad[-mbedtls] and luci exposes a number of 802.11k (and 802.11v) configuration options.
Why would (at least some of) these be exposed under wpad-basic[-wpad]?
Is this because without the ability to populate the neighbor information, this wouldn't make sense (given I am using an additional source to provide it)? Or is there something else that I am missing?
Given that my network doesn't change, I don't need active RRM measurement & automatic population. I am happier with openwrt-rrm-nr-disrtibutor and could even use the package static-neighbor-reports.
Thanks @brada4. What do you mean by "instrument"? Does this include?
Each AP determining & sharing the neighbor information for other APs to advertise & sharing this.
Each AP working out what neighbors are sensible to advertise & doing so.
Having a central/shared overview of the network, how roaming is working and optimising this.
In my instance, I believe/hope openwrt-rrm-nr-distributor is doing the bits I need from this for me. I have only three APs in a configuration that doesn't change. And my main purpose is not to have call dropouts when walking from one side of the house to the other.
Thanks also @robimarko, I gathered as much, but if the functionality is there, why not expose it? Which is what I am trying to understand with @brada4 and others' help.
You asked why, you got 2 answers 1/ size 2/ not useful without extra software.
So you msde a decision your userland can use it, and installed bigger and more functional hodtapd. Thats it.
It is useful without extra software. Some WiFi stations are able to ask AP for a list of neighboring networks when deciding if it’s time to roam. This only depends on station. For this query to work, this list needs to be filled by the aforementioned distributor. Also usteer and dawn fill it. However, usteer filters BSSIDs to only include 5 GHz ones.
I didn’t have good experience with the distributor because it was breaking down after running for some time. I couldn’t find the culprit so I switched to usteer with kicking disabled.