Band Steering: How an AP Moves Clients to 5 GHz
Watch how a dual-band AP moves clients from 2.4 GHz to 5 GHz: unanswered probes, associations refused with status code 82 and 802.11v BTM requests, and why steering a client too far from the AP makes it slower.
How to use this tool controls and what to look for
Pick a client and a steering method, drag the client away from the AP, and watch the frames that decide whether it joins 2.4 GHz or 5 GHz.
Controls to change
- Client: compare a Wi-Fi 6 phone, a Wi-Fi 5 laptop, an older dual-band client that prefers 2.4 GHz, and a 2.4 GHz-only IoT sensor.
- Steering method: choose Off, Hide 2.4 GHz probe responses, Reject 2.4 GHz association, or 802.11v BTM request.
- 5 GHz steering threshold: the weakest 5 GHz probe the AP will still steer; lower it to steer clients further away.
- Max steering attempts: how many 2.4 GHz probes or association attempts the AP turns away before it lets the client in.
What to look for
- The frame sequence: which probes go unanswered, which association is refused with status 82, and where the client ends up.
- Time added to connect: with the older client, steering can cost a second or more, or give up and let it join 2.4 GHz anyway.
- Set the threshold to −85 dBm and drag the client to about 30 m: it is still steered to 5 GHz, but it is slower both ways than on 2.4 GHz.
- The charts show where 5 GHz stops being faster in each direction, and how far your threshold steers.
About this tool
A dual-band access point sends the same network name on 2.4 GHz and 5 GHz, and the client, not the AP, chooses which band to join. Many clients pick 2.4 GHz because its signal looks stronger, even though 5 GHz has more and wider channels. Band steering is the AP nudging that choice: it can leave the client's 2.4 GHz probes unanswered, refuse it on 2.4 GHz with status code 82 and a neighbor report, or ask a connected client to move with an 802.11v BSS Transition Management request. This simulator shows the frames each method sends for a Wi-Fi 6 phone, a Wi-Fi 5 laptop, an older dual-band client and a 2.4 GHz-only IoT sensor, how much time each adds to connecting, and where steering starts to make a client slower than it would be on 2.4 GHz.
What you'll learn
- Why a dual-band client often picks 2.4 GHz, and why the AP can only influence that choice, not make it
- How hiding 2.4 GHz probe responses, refusing association with status code 82 and 802.11v BTM requests each steer a client, and which clients ignore them
- Why band steering can add a second or more to connecting, and what the steering attempt limit trades off
- How to pick a 5 GHz steering threshold, and why a client steered too far from the AP is slower both ways
Common questions
Is band steering part of the IEEE 802.11 standard?
No. Band steering is each vendor's own logic. It is built from standard frames: probe responses, authentication and association responses with status code 82 (REJECTED_WITH_SUGGESTED_BSS_TRANSITION) and 802.11v BSS Transition Management requests, but when and how the AP uses them is up to the vendor.
Should I turn band steering on?
For most enterprise networks, yes, with a sensible 5 GHz signal threshold and a small attempt limit, so capable clients use 5 GHz without long connection delays. Many recent clients already prefer 5 GHz on their own. Watch for older or IoT clients that connect slowly or fail, and remember that 2.4 GHz-only devices are never steered.
Why do some clients still connect on 2.4 GHz with band steering on?
The client may have no 5 GHz radio, the AP may not have heard its 5 GHz probes, its 5 GHz signal may be below the steering threshold, or the AP may have given up after its attempt limit. A client can also ignore a BTM request, or not support 802.11v at all.
Free for private and educational use. This interactive model is a simplified teaching aid and may contain mistakes. It is provided as is, without warranty. Use it to understand the concepts, not as a substitute for a site survey, vendor documentation or professional design advice.