Some non-Intel clients, for example, when set to LEAP, cannot authenticate in this case.
However, the Intel Wireless LAN client can authenticate, if the Rogue AP is unchecked.
Rogue AP Checkbox configuration
When the checkbox is checked it ensures that the client implements the Rogue AP
feature as required by CCX. The client makes note of APs that it failed to authenticate
with and sends this information to the AP that allows it to authenticate and connect. Also,
the supplicant sets the Authentication algorithm type to 0x80 when the Rogue AP box is
checked. There may be some network configurations implementing and
as described above. For this setup to work, the client must use an
Authentication Algorithm value of 0x0, as opposed to the need to use 0x80 for
described above. Therefore, the Rogue AP checkbox also enables the client to
support Network-EAP only and Open and Required EAP only.
Cisco CCX Feature Support
The Cisco mandatory Client Compliance Specifications Version1.0:
●
Compliance to all mandatory items of 802.11
●
De-fragmentation of MSDUs and MMPDUs
●
Generate CTS in response to an RTS
●
Open and Shared key authentication support
●
Support Active scanning
●
Wi-Fi compliance required
●
On Windows platforms, Microsoft 802.11 NIC compliance
●
802.1X-2001 Compliance
●
EAP-TLS (Transport Level Security, RFC 2716) support on Windows XP
●
EAP-MD4 (RFC 1320) support on Windows XP
●
EAP packets to be sent unencrypted
●
Broadcast key rotation support
●
CKIP support
