[NEBULA] How to share AP loading to optimize wireless performance?
The wireless performance decreases if the loading of AP is too heavy. Nebula provides two load balancing modes to balance network traffic among multiple APs to resolve poor Wi-Fi connectivity due to AP overloading.
Distribute wireless traffic across multiple APs to share the loading on network by detecting number of connected stations. Configure Load balancing at Access Point > Configure > AP & port settings > Load balancing to achieve it.
The default setting is Disable. For general use, we recommend to use “By client device number” mode. Enter the threshold number of client devices at which AP begins load balancing its connections. Select Disassociate client device when overload to disassociate wireless clients connected to the AP when it becomes overloaded. The disassociation priority is the client with longest idle time then shift to client with weak signal strength.
Note: AP delays sending response, authentication and probe request to disassociated stations up to 3 times. Disassociated station is allowed to reconnect by receiving 3 times of delayed response. Reconnected station will no longer be disassociated.
If you have E-learning scenario, we recommend to enable “Smart Classroom” mode. Enter the threshold number of client devices at which AP begins load balancing its connections. The AP kicks excessive clients instantly and ignores response, authentication and probe request packets from any client device when the maximum number of client devices is reached. Disassociate client device when overload is default enabled and disassociation priority is always signal strength.
Note: AP auto-detects if there are other APs that can provide service and will always allow client connection if no other AP is available.