WA6520 Cloudnet WLAN MAC authentication failure due to incorrect configuration

Cloud AP

When the handheld terminal connects to the dedicated SSID, it shows successful association but fails to obtain an IP address, and the terminal remains in standby mode. 2. The same terminal can obtain an IP address normally when connecting to other SSIDs.

1. Network Topology and DHCP Verification: Confirm that the VLAN permission configuration on the LAN side is correct, the DHCP service on the core switch runs normally, and other terminals can obtain IP addresses properly, which rules out DHCP server failures and VLAN transparent transmission issues. 

2. Authentication Method Analysis: Confirm that the faulty SSID uses MAC address whitelist authentication (without a RADIUS server), and terminal MAC addresses are imported in bulk via an Excel file. Inspection reveals an abnormal configuration in the MAC address mask field of the imported file; the customer mistakenly filled in the MAC address itself as the mask value. 

3. Verification of MAC Mask Configuration Principles: In accordance with Cloudnet MAC address matching rules, the mask is used to specify the number of matching bits:

 ◦ Match the first 16 bits (OUI vendor code): ffff-0000-0000

 ◦ Match the first 24 bits: ffffff-0000-0000

 ◦ Exact 48-bit match (full MAC address): ffff-ffff-ffff

 ◦ Match the first 12 bits: fff0-0000-0000 

The mask value configured by the customer does not comply with the above rules, resulting in whitelist matching failures. Although terminals associate with the SSID, authentication cannot pass, so the DHCP process cannot be initiated.

Correct the MAC address mask configuration: Edit the MAC address whitelist on the Cloudnet platform, and change the incorrect MAC address value in the mask field to the exact matching value ffff-ffff-ffff (if full MAC address matching is required).