You are not logged in.

#1 2019-05-13 12:44:41

XDarkAngelX
Member
Registered: 2014-01-08
Posts: 60

wpa_supplicant 2:2.8-1 fails to connect to PEAP MSCHAPv2 networks

After the update to wpa_supplicant 2:2.8-1 from wpa_supplicant 2:2.6-2  my laptop fails to connect to my collage network, after downgrading to wpa_supplicant 2:2.6-2 my laptop succeed in connecting to the collage network
My collage network uses PEAP MSCHAPv2 to authenticate

Any idea what changed in wpa_supplicant 2:2.8-1 causing it to fail to authenticate to the collage network?

Offline

#2 2019-05-13 15:34:58

loqs
Member
Registered: 2014-03-06
Posts: 8,169

Re: wpa_supplicant 2:2.8-1 fails to connect to PEAP MSCHAPv2 networks

Possibly the same issue as when wpa_supplicant previously moved from openssl-1.0 to openssl 1.1 [1]

[1] https://bugs.archlinux.org/task/54390

Offline

#3 2019-05-14 06:38:16

XDarkAngelX
Member
Registered: 2014-01-08
Posts: 60

Re: wpa_supplicant 2:2.8-1 fails to connect to PEAP MSCHAPv2 networks

The issue seems to be really the move from openssl-1.0 to openssl 1.1 , I tried building wpa_supplicant 2:2.8 with openssl-1.0 and it succeed connecting to the collage network

Offline

#4 2019-05-17 19:43:53

srhathorn
Member
Registered: 2018-08-22
Posts: 1

Re: wpa_supplicant 2:2.8-1 fails to connect to PEAP MSCHAPv2 networks

I'm experiencing issues with wpa_supplicant 2:2.8 as well.

It seems like its actually related to this bug
https://bugs.archlinux.org/task/61119

Looks like it was reported to wpa_supplicant and brcmfmac maintainers in Dec/Jan but still has not been fixed upstream.

Downgrading to 2.6 fixes the problem for me.

Offline

#5 2019-05-17 22:14:00

loqs
Member
Registered: 2014-03-06
Posts: 8,169

Re: wpa_supplicant 2:2.8-1 fails to connect to PEAP MSCHAPv2 networks

@srathorn was the brcmfmac issue not addressed by:
https://w1.fi/cgit/hostap/commit/?id=43 … 2a9197593e
https://w1.fi/cgit/hostap/commit/?id=d8 … f62b070d47
the second issue from 61119 affecting broadcom wl users was addressed by CONFIG_FILS no longer being specified but I it may not have been reported upstream.

Offline

Board footer

Powered by FluxBB