Client
: In this case the client needs to send out an authentication algorithm value of 0x80
else the 802.11 authentication handshake would fail. During boot, when the Wireless
LAN driver is already loaded, but the Intel(R) PROSet supplicant is still unloaded, the
client sends 802.11 authentication with an Authentication algorithm value of 0x0. Once
the Intel(R) PROSet supplicant loads, and engages the LEAP profile, it sends 802.11
authentication with an Authentication algorithm value of 0x80.
However, the supplicant
sends out 0x80 only if the Rogue AP box is checked.
Network-EAP, Open and Required EAP
AP
: If Network-EAP, Open and Required EAP boxes are checked then it would accept
both types of 802.11 authentication algorithm values 0x0 and 0x80. However, once the
client is associated and authenticated the AP expects an EAP handshake to take
place. For any reason if the EAP handshake does not take place quickly, the AP would
not respond to the client for about 60 seconds.
Client
: Here the client could send out an authentication algorithm value of 0x80 or 0x0.
Both values are acceptable and the 802.11 authentication handshake would succeed.
During boot, when the Wireless LAN driver is already loaded and the client sends 802.11
authentication with an Authentication algorithm value of 0x0. This is sufficient to get
authenticated but the corresponding EAP or LEAP credentials need to be communicated
to the AP to establish a connection.
Open and Required EAP only
AP
: In the case where the AP is configured with Network-EAP unchecked, but Open and
Required EAP checked, the AP will reject any client attempting to 802.11 authenticate
using an authentication algorithm value of 0x80. The AP would accept any client using an
authentication algorithm value of 0x0, and expects EAP handshake to commence soon
after. In this case, the client uses MD5, TLS, LEAP or any other appropriate EAP method
suitable for the specific network configuration.
Client
: The client in this case is required to send out an authentication algorithm value of
0x0. As mentioned before the sequence involves a repeat of the initial 802.11
authentication handshake. First, the Wireless LAN driver initiates authentication with a
value of 0x0 and later the supplicant would repeat the process. However, the
authentication algorithm value used by the supplicant depends status of the Rogue AP
checkbox.
When the Rogue AP box is unchecked
, the client sends an 802.11
authentication with
Authentication algorithm value of 0x0
even after the supplicant
loads and engages the LEAP profile.
