How does Ruckus Band-Steering work?
Band-steering Design introduces a data structure shared by both radios of an AP.
In the structure, APs maintain a table of clients.
Update the table with each detected probe request.
Remember whether the client has dual-band capability.
Measure average RSSI per band, within the last minute.
Limit table size, delete inactive entries.
Check the table before responding to 1) Probe Requests, 2) Authentication requests
Band steering is enabled by
default and the default threshold value is 20 db. If the client Ruckus detected by
"probes" (looking for AP's) in both 5GHz and 2.4GHz has good power in
both, the AP with "band steering" on, will respond only with
"probe response" in the 5GHz for the client where connected to that
radio.
RSSI threshold values:
Typical:
20
Steer
all: 1
Disable:
0
Values
are persistent at each AP per WLAN
rkscli:
get band-steering-rssi-thresh
wlan
set band-steering-rssi-thresh
wlan
Refusing Authentication:
If client requests authentication on 2.4g, and
AP has previously detected client on 5g, and
Client does not appear to be in distress
- sufficient RSSI[1] on 5g within the past minute, or else
- sufficient RSSI[2] on 2.4g within the past minute, and
AP is not a Mesh AP, then
refuse authentication on 2.4g
[1] Threshold for 5g is the CLI value for this WLAN
[2] Threshold for 2.4g is the CLI value plus adjustment per client when AP has concurrent measurements.
Withholding Probe Responses:
If client is probing on 2.4g, and
AP previously detected the client on 5g, and
One of the following
- AP has not detected probes from client in past minute, or
- Client does not appear to be in distress (see Auth Refusal), and
AP is not a Mesh AP, then
withhold probe response on 2.4g.
Note: Clients try to authenticate even when the AP does not respond to its probes, so withholding probe responses alone is not sufficient to steer clients.