I am currently doing some tests with wpa_supplicant and hostapd and I am facing a quite strange connection/disconnection problem when using WPA2.
When the WiFi client (using wpa_supplicant) tries to associate to the AP (managed by hostapd) is several times disconnected from the network before finally receiving an IP address and finally being able to transmit data.
Apparently, the client is 1st correctly associated (message “State: ASSOCIATING -> ASSOCIATED” visible in the wpa_supplicant log) but the client is soon after disconnected due to authentication problem with the following error message:
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
Authentication with 00:0e:8e:3b:05:6d timed out.
BSSID 00:0e:8e:3b:05:6d blacklist count incremented to 2
No keys have been configured - skip key clearing
State: ASSOCIATED -> DISCONNECTED.
After this the client restarts the association/authentication procedure and after a few tries the authentication succeed. The SSID of the base was well broadcasted during the above described test.
Up to now, I have never seen this problem when connecting without authentication.
I can connect without problem with Windows PC with WPA2 enabled, so I would suspect that the AP is correctly configured.
Would anyone know the reason for this “connection/disconnection” problem?
Would this be a known issue or is it related to incorrect configuration of hostapd or wpa_supplicant (relevant part of the config files are given below)?
Thanks in advance for any help.
Wpa_supplicant at error time:
Hostapd at error time:
##### WPA/IEEE 802.11i configuration
wpa=2 #for WPA2 encryption