Arch Linux

oxygen_wobble

Member

Registered: 2012-05-20

Posts: 128

Eduroam stopped working after latest update

Hi,

so, i updated my system recently (like i frequently do), and since then i can't connect to eduroam any longer,
which was working totally fine and stable before.

The phenomenom is basically the same on both my main laptop (using NetworkManager) as well as on my
backup system (using netctl). With netctl, i use a wpa-configsection profile.

Both have an intel chipset and use iwlwifi.

Both were working fine before the update.

Both work fine with simple WPA-PSK networks.

My eduroam account is valid and works on my phone.

It doesn't make a difference whether i use dhcpcd or dhcclient. 

So, anybody's got a hint for me ?

Regards,
n

zuglufttier

Member

Registered: 2015-07-12

Posts: 4

Re: Eduroam stopped working after latest update

I'm using eduroam, too, but I don't have any problems... I updated a few hours ago. We need some kind of log!

Please open a terminal and enter "journalctl -xf", then open another terminal and enter "sudo systemctl restart NetworkManager.service".

In the first terminal, you should see some infos regarding the networking and there should be some kind of error...

oxygen_wobble

Member

Registered: 2012-05-20

Posts: 128

Re: Eduroam stopped working after latest update

I'm on the backup system, so here it says with netctl:

systemctl status netctl@eduroam.service

 netctl@eduroam.service - Networking for netctl profile eduroam
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fr 2016-10-14 16:17:19 CEST; 10s ago
     Docs: man:netctl.profile(5)
  Process: 11996 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 11996 (code=exited, status=1/FAILURE)

Okt 14 16:16:47 kuroneko systemd[1]: Starting Networking for netctl profile eduroam...
Okt 14 16:16:47 kuroneko network[11996]: Starting network profile 'eduroam'...
Okt 14 16:17:19 kuroneko network[11996]: WPA association/authentication failed for interface 'wls1'
Okt 14 16:17:19 kuroneko network[11996]: Failed to bring the network up for profile 'eduroam'
Okt 14 16:17:19 kuroneko systemd[1]: netctl@eduroam.service: Main process exited, code=exited, status=1/FAILURE
Okt 14 16:17:19 kuroneko systemd[1]: Failed to start Networking for netctl profile eduroam.
Okt 14 16:17:19 kuroneko systemd[1]: netctl@eduroam.service: Unit entered failed state.
Okt 14 16:17:19 kuroneko systemd[1]: netctl@eduroam.service: Failed with result 'exit-code'.

journalctl -xe

Okt 14 16:16:50 kuroneko kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wls1: link becomes ready
Okt 14 16:16:50 kuroneko kernel: wls1: Limiting TX power to 30 (30 - 0) dBm as advertised by 94:b4:0f:fd:66:d0
Okt 14 16:16:53 kuroneko kernel: wls1: deauthenticating from 94:b4:0f:fd:66:d0 by local choice (Reason: 3=DEAUTH_LEAVING)
Okt 14 16:17:05 kuroneko kernel: wls1: authenticate with 94:b4:0f:85:ca:b0
Okt 14 16:17:05 kuroneko kernel: wls1: send auth to 94:b4:0f:85:ca:b0 (try 1/3)
Okt 14 16:17:05 kuroneko kernel: wls1: authenticated
Okt 14 16:17:05 kuroneko kernel: wls1: associate with 94:b4:0f:85:ca:b0 (try 1/3)
Okt 14 16:17:05 kuroneko kernel: wls1: RX AssocResp from 94:b4:0f:85:ca:b0 (capab=0x1011 status=0 aid=2)
Okt 14 16:17:05 kuroneko kernel: wls1: associated
Okt 14 16:17:06 kuroneko kernel: wls1: Limiting TX power to 23 (23 - 0) dBm as advertised by 94:b4:0f:85:ca:b0
Okt 14 16:17:09 kuroneko kernel: wls1: deauthenticating from 94:b4:0f:85:ca:b0 by local choice (Reason: 3=DEAUTH_LEAVING)
Okt 14 16:17:19 kuroneko network[11996]: WPA association/authentication failed for interface 'wls1'
Okt 14 16:17:19 kuroneko network[11996]: Failed to bring the network up for profile 'eduroam'
Okt 14 16:17:19 kuroneko systemd[1]: netctl@eduroam.service: Main process exited, code=exited, status=1/FAILURE
Okt 14 16:17:19 kuroneko systemd[1]: Failed to start Networking for netctl profile eduroam.
-- Subject: Unit netctl@eduroam.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@eduroam.service has failed.
-- 
-- The result is failed.
Okt 14 16:17:19 kuroneko systemd[1]: netctl@eduroam.service: Unit entered failed state.
Okt 14 16:17:19 kuroneko systemd[1]: netctl@eduroam.service: Failed with result 'exit-code'.

When using wpa_supplicant as standalone:

Successfully initialized wpa_supplicant
wls1: SME: Trying to authenticate with 94:b4:0f:fd:66:d0 (SSID='eduroam' freq=5500 MHz)
wls1: Trying to associate with 94:b4:0f:fd:66:d0 (SSID='eduroam' freq=5500 MHz)
wls1: Associated with 94:b4:0f:fd:66:d0
wls1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wls1: CTRL-EVENT-EAP-STARTED EAP authentication started
wls1: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=21 -> NAK
wls1: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
TLS: Unsupported Phase2 EAP method 'MSCHAPv2'
wls1: EAP: Failed to initialize EAP method: vendor 0 method 25 (PEAP)
wls1: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wls1: Authentication with 94:b4:0f:fd:66:d0 timed out.
wls1: CTRL-EVENT-DISCONNECTED bssid=94:b4:0f:fd:66:d0 reason=3 locally_generated=1
wls1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="eduroam" auth_failures=1 duration=10 reason=AUTH_FAILED
wls1: CTRL-EVENT-SSID-REENABLED id=0 ssid="eduroam"
wls1: SME: Trying to authenticate with 94:b4:0f:85:ca:b0 (SSID='eduroam' freq=5260 MHz)
wls1: Trying to associate with 94:b4:0f:85:ca:b0 (SSID='eduroam' freq=5260 MHz)
wls1: Associated with 94:b4:0f:85:ca:b0
wls1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wls1: CTRL-EVENT-EAP-STARTED EAP authentication started
wls1: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=21 -> NAK
wls1: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
TLS: Unsupported Phase2 EAP method 'MSCHAPv2'
wls1: EAP: Failed to initialize EAP method: vendor 0 method 25 (PEAP)
wls1: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wls1: Authentication with 94:b4:0f:85:ca:b0 timed out.
wls1: CTRL-EVENT-DISCONNECTED bssid=94:b4:0f:85:ca:b0 reason=3 locally_generated=1
wls1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="eduroam" auth_failures=2 duration=23 reason=AUTH_FAILED

oxygen_wobble

Member

Registered: 2012-05-20

Posts: 128

Re: Eduroam stopped working after latest update

I wonder why MSCHAPv2 is not supported ? Hasn't been a problem before, anyway ...

The other messages don't seem particularly helpful .. .

oxygen_wobble

Member

Registered: 2012-05-20

Posts: 128

Re: Eduroam stopped working after latest update

Ok, downgrading to an older version of wpa_supplicant helped, seems to be related to this bug:

https://bugs.archlinux.org/task/48327

Not the ideal solution, but i've got more important things in my head now, so i'll come back to this later ...

cmlr

Member

From: Rochester, NY, USA

Registered: 2007-04-18

Posts: 99

Re: Eduroam stopped working after latest update

There is a bug in wpa_supplicant 2.6.

http://lists.infradead.org/pipermail/ho … 36460.html

r00tr4t

Member

Registered: 2013-01-16

Posts: 100

Re: Eduroam stopped working after latest update

Confirmed that 2.6 do not work on our Eduroam WiFi but downgrading from 2.6-1 to 2.5-3 solves the issue.
Downgrade by:

 sudo pacman -U /var/cache/pacman/pkg/wpa_supplicant-1:2.5-3-x86_64.pkg.tar.xz 

R00KIE

Forum Fellow

From: Between a computer and a chair

Registered: 2008-09-14

Posts: 4,734

Re: Eduroam stopped working after latest update

You should also test the latest git and see if the problem is already fixed there. If the problem is fixed and you can bisect to see what fixed it then you can submit a bug report explaining the problem and indicating which commit fixes the problem.

---

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Archange

Package Maintainer (PM)

Registered: 2014-08-17

Posts: 40

Re: Eduroam stopped working after latest update

Affected too…

The error lines are:

TLS: Unsupported Phase2 EAP method 'MSCHAPv2'
wlp6s0: EAP: Failed to initialize EAP method: vendor 0 method 25 (PEAP)

cmlr

Member

From: Rochester, NY, USA

Registered: 2007-04-18

Posts: 99

Re: Eduroam stopped working after latest update

According to this bug discussion, you should change your configuration from

'phase2="auth=MSCHAPv2"'

to

'phase2="auth=MSCHAPV2"'

That is, capitalize the letter "V".

Last edited by cmlr (2016-11-07 20:55:10)