Why users are associated with other APs when AP density is high

2

The reason is that the interval between sending Beacon frames is long. A STA obtains peripheral wireless network information in either of the following ways:
- Passive scan: A STA listens on the Beacon frames sent by APs to obtain wireless network information.
- Active scan: A STA actively sends a Probe Request frame and receives Probe Response frames to obtain wireless signals.

A STA can actively and passively scan wireless networks. When a STA passively scans wireless networks and the AP density is high, the STA can receive Beacon frames from another AP, not the nearest AP and perform association.

Other related questions:
STAs are associated with other APs in multi-AP scenarios
In multi-AP scenarios, STAs may be associated with other APs when a long Beacon frame transmission interval is set. STAs obtain information about peripheral WLANs in either of the following ways: - Passive scan: STAs scan Beacon frames sent by surrounding APs to obtain WLAN information. - Active scan: STAs actively send Probe Request frames and receive Probe Response frames to obtain wireless signals. STA can actively or passively scan surrounding WLANs. When a STA passively scans WLANs and APs are densely deployed, the STA can receive Beacon frames from another AP but not the nearest AP, and perform association.

Why cannot STAs associate with an AP when WEP authentication is used
The possible causes are as follows: - No WEP SSID is added to the STA. Many STAs associate with WEP SSIDs by using encryption without authentication. However, the AP uses both authentication and encryption. Therefore, the STA cannot associate with the SSID. The SSID must be manually configured on the STA. At last, set the encryption type to share mode. - The key index configured on the AP is different from the key index on the STA. By default, the key index of an AP is 0 (ranging from 0 to 3), and the key index of STA is 1 (ranging from 1 to 4). Key index 0 on the AP matches key index 1 on the STA.

How do I view information about the AP with which a STA associates
To display information about the AP with which a STA associates, run the following command: display access-user mac-address x-x-x The following information including the AP ID is displayed: Basic: User ID : 365 User name : e005c5fab829 Domain-name : default User MAC : e005-c5fa-b829 //MAC address of the user User IP address : 192.168.130.254 //IP address of the user User access Interface : Wlan-Dbss1:0 QinQVlan/UserVlan : 0/130 //User VLAN User access time : 2013/03/06 19:52:29 User accounting session ID : AC66050000000000013066b6c7000365 User access type : WEB Terminal Device Type : Data Terminal AP ID : 0 //ID of the connected AP AP name : ap-0 Radio ID : 0 //Access frequency band: 0 indicates 2.4G, and 1 indicates 5G. AP MAC : 0046-4b74-68c0 //AP mac SSID : test //SSID name Online time : 59(s)

Why cannot STAs associate with an AP when WPA-PSK authentication is used
The possible causes are as follows: - The AC's interface connecting to the switch or AP is not added to service VLANs. During the authentication, keys need to be exchanged through the service channel; therefore, the interfaces must be added to service VLANs. - The STA does not support WPA2-PSK. For example, the computer runs an early version of Windows XP without patches installed, the computer may not support WPA2-PSK. Patches need to be installed on the computer.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top