Why can the AP be connected with more than one station with load balancing?





The wireless load balancing function is designed to delay the responses to client probe requests when the AP is overloaded.
New clients could eventually associate with the AP if there is no other AP to connect to or they always choose to connect to the same AP.
The difference is enabling or disabling Disassociate station when overloaded function on AP.
Its mechanism is described as following:
1. When the AP is overloaded, the system checks all associated stations’ idle times, and selects the longest idle one as the victim.
2. If the system can’t find the longest idle station, it will select the station with the minimum signal strength.
3. If a selected station matches the above cases but it has been existed in the “kicked cache” (it means the station had been kicked out recently), the system will select another station to kick out.
If the station always chooses to connect the same AP when the AO is overload, the AP delays sending probe and authentication response to disassociated stations up to 3 times.
Disassociated station is allowed to reconnect after 3 times.
Categories
- All Categories
- 199 Beta Program
- 1.8K Nebula
- 94 Nebula Ideas
- 63 Nebula Status and Incidents
- 4.7K Security
- 236 Security Ideas
- 1.1K Switch
- 52 Switch Ideas
- 919 WirelessLAN
- 28 WLAN Ideas
- 5.4K Consumer Product
- 173 Service & License
- 296 News and Release
- 65 Security Advisories
- 14 Education Center
- 1K FAQ
- 454 Nebula FAQ
- 258 Security FAQ
- 100 Switch FAQ
- 115 WirelessLAN FAQ
- 22 Consumer Product FAQ
- 70 Service & License FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 69 About Community
- 52 Security Highlight