Arch Linux

41418

Member

Registered: 2015-01-13

Posts: 11

Unable to connect to WPA2-EAP after update

Hi all.
A couple days ago, I ran a system update (sudo pacman -Syu) and it seems that afterwards, I am no longer able to connect to WPA2 Enterprise networks.  I don't know if the 2 events are related, but that is the only thing that has changed from when it was working to when it wasn't.

From the RADIUS server I am seeing successful authentications, through wpa_cli, I am seeing:

<3>CTRL-EVENT-EAP-SECCUSS EAP authentication completed successfully
<3>RSN: PMKID mismatch - authentication server may have derived different MSK?!
<3>CTRL-EVENT-DISCONNECTD bssid=xx:xx:xx:xx:xx:xx reason=1 locally_generated=1

I have 2 WPA2 Enterprise networks that I connect to, and both are no longer working.  Other modes of wifi are working.

Below is one of the wpa_supplicant files that was previously working:

ctrl_interface=DIR=/run/wpa_supplicant
network={
    ssid="MySSID"
    key_mgmt=WPA-EAP IEEE8021X
    eap=PEAP
    identify="username"
    password="password"
}

Last edited by 41418 (2015-12-14 06:01:43)

perlatus

Member

Registered: 2016-01-22

Posts: 1

Re: Unable to connect to WPA2-EAP after update

I am getting this exact error also, although I wasn't able to successfully connect to the access point earlier.

rumpelsepp

Member

From: Bavaria

Registered: 2012-11-13

Posts: 105

Website

Re: Unable to connect to WPA2-EAP after update

Hi!

Seems to be an wpa_supplicant bug. Downgrading to wpa_supplicant 2.3 solves the issue for me.
See also this: http://permalink.gmane.org/gmane.linux. … stap/34340

---

Every time I see some piece of medical research saying that caffeine is good for you, I high-five myself. Because I'm going to live forever. -- Torvalds, Linus (2010-08-03).