I have the impression that the missing information in MT does not allow to estimate if it is getting crowded or not. Other brands clearly use this info for AP and band steering. The client decides (as always in wifi) but is given (QBSS load element) some information to help in that decision. With MT I did not find this in the beacon. But even within ROS I did not find that information, unless stopping the AP and doing "Freq Usage" scan. The process of CCA (clear channel assessment) happens before every transmit, so ROS could know, but that information is not at our disposal AFAIK.@solarium14
How do you measure thet 2.4GHz "gets crowded"? Number of devices? Traffic? Signal quality?
You can write a script which counts devices connected to 2.4 bands and then change ACL to drop block new connections or drop all these with quality below limits to "persuade" them to reconnect to better quality band.
Why script it, wlan interface has Max station Count option so you can limit number of devices there, other vendors do this by default as i saw on some (Aruba for ex)@solarium14
How do you measure thet 2.4GHz "gets crowded"? Number of devices? Traffic? Signal quality?
You can write a script which counts devices connected to 2.4 bands and then change ACL to drop block new connections or drop all these with quality below limits to "persuade" them to reconnect to better quality band.
Well what can you do about this client?If hes that far, he will probable have worse signal or no signal on 5ghz..Yes you can restrict the number of clients. But it is for me by no means a measure for the load on that AP. 100 clients that are quiet give almost no load (happens more these days than some time ago with smartphones, smartwatches etc). 1 client, from far away, transmitting or receiving at 6 Mbps, can be an enormous load (consumption of air-time) even for a limited amount of data.