[Networkmanager] Cannot connect to an AP managed with NM and WPA
krystianheberlein at gmail.com
Wed Dec 21 18:02:57 UTC 2022
Recently I was struggling to establish a connection with a WiFi Access
Point managed by NetworkManager with WPA supplicant plugin.
Although most available devices are able to connect with the AP, my
RasberryPi 4B won't cooperate.
On the RPi4 I'm trying to connect as a client with WPA supplicant, but
constantly the association gets rejected:
wpa on the client side:
wlan0: Trying to associate with SSID 'AP-NAME'
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=11:22:33:44:55:66 status_code=16
wpa on AP side:
Searching a PSK for 11:22:33:44:55:66 prev_psk=0x5d46ac
hostapd_logger: STA 11:22:33:44:55:66 - invalid MIC in msg 2/4 of 4-Way
wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 11:22:33:44:55:66
hostapd_logger: STA 11:22:33:44:55:66 - EAPOL-Key timeout
WPA: 11:22:33:44:55:66 WPA_PTK entering state PTKSTART
hostapd_logger: STA 11:22:33:44:55:66 - PTKSTART: Retry limit 4 reached
WPA: 11:22:33:44:55:66 WPA_PTK entering state DISCONNECT
wpa_sta_disconnect STA 11:22:33:44:55:66 (reason 15)
An interesting fact is that I'm able to connect to the Access Point if AP
is created with wpa_supplicant only.
Another observation is that connection is established successfully if both
ends are running the NetworkManager,
i.e. the AP is managed by NM and the client connects with the AP using NM.
How does the NM change the wpa_supplicant configuration that might cause
this kind of problem?
Do you have some suggestions regarding the wpa_supplicant or NM
The Access Point runs NetworkManager 1.38.0 and wpa_supplicant 2.10
The client is using wpa_supplicant 2.10.
The Access Point profile:
Thanks in advance!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Networkmanager