802.11k/v works well enough but the problem is when you are roaming the device is likely to see 2.4ghz network before it sees 5ghz network. Unless the manufacturers considered this scenario, the device will connect to 2.4ghz and remain connected to that instead of upgrading to higher bands. You need usteer in these situations.
You can also kind of patch this problem by setting beacon interval for 5/6ghz networks shorter than beacon interval for 2.4ghz network.
Also the problem with usteer is, they took the easy way out and do broadcast for syncing with other usteer instances instead of multicast so it's a lot of wasted bandwidth and it'll hit all the devices in that l2 segment.
Thanks for the info!
I didn't know about the multicast "storm" in usteer. I had a look at dawn too, but that one doesn't seem to support limiting its functionality to a specified subset of wifi interfaces.
1. https://github.com/openwrt/openwrt/issues/9181
2. https://github.com/openwrt/openwrt/issues/9071
802.11k/v works well enough but the problem is when you are roaming the device is likely to see 2.4ghz network before it sees 5ghz network. Unless the manufacturers considered this scenario, the device will connect to 2.4ghz and remain connected to that instead of upgrading to higher bands. You need usteer in these situations.
You can also kind of patch this problem by setting beacon interval for 5/6ghz networks shorter than beacon interval for 2.4ghz network.
Also the problem with usteer is, they took the easy way out and do broadcast for syncing with other usteer instances instead of multicast so it's a lot of wasted bandwidth and it'll hit all the devices in that l2 segment.