You are not logged in.

Pages: 1

#1 2015-08-06 13:42:14

Compizfox
Member
Registered: 2015-08-06
Posts: 20

WPA2 Enterprise (EAP) issues with Thinkpad W540

Hi,

Suddenly (probably since an update) I'm not able to connect to 802.1x EAP wireless networks on my Thinkpad W540. It has worked like it should in the past, and it still works exactly one time after a reboot. However, if I disconnect from the network and try to reconnect, or after a wake from standby, I'm not able to connect anymore. This is the error:

aug 07 23:55:40 LARS-SURKESH kernel: wlp3s0: authenticate with 54:e6:fc:fa:c3:4e
aug 07 23:55:40 LARS-SURKESH kernel: wlp3s0: send auth to 54:e6:fc:fa:c3:4e (try 1/3)
aug 07 23:55:40 LARS-SURKESH kernel: wlp3s0: authenticated
aug 07 23:55:40 LARS-SURKESH kernel: wlp3s0: associate with 54:e6:fc:fa:c3:4e (try 1/3)
aug 07 23:55:40 LARS-SURKESH NetworkManager[473]: <info>  (wlp3s0): supplicant interface state: scanning -> associating
aug 07 23:55:40 LARS-SURKESH kernel: wlp3s0: RX AssocResp from 54:e6:fc:fa:c3:4e (capab=0x431 status=0 aid=4)
aug 07 23:55:40 LARS-SURKESH kernel: wlp3s0: associated
aug 07 23:55:40 LARS-SURKESH kernel: cfg80211: Calling CRDA for country: NL
aug 07 23:55:40 LARS-SURKESH kernel: cfg80211: Regulatory domain changed to country: NL
aug 07 23:55:40 LARS-SURKESH kernel: cfg80211:  DFS Master region: ETSI
aug 07 23:55:40 LARS-SURKESH kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
aug 07 23:55:40 LARS-SURKESH kernel: cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
aug 07 23:55:40 LARS-SURKESH kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
aug 07 23:55:40 LARS-SURKESH kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
aug 07 23:55:40 LARS-SURKESH kernel: cfg80211:   (5490000 KHz - 5710000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s)
aug 07 23:55:40 LARS-SURKESH kernel: cfg80211:   (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
aug 07 23:55:40 LARS-SURKESH NetworkManager[473]: <info>  (wlp3s0): supplicant interface state: associating -> associated
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='redacted'
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=54:e6:fc:fa:c3:4e reason=3 locally_generated=1
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: SME: Trying to authenticate with 54:e6:fc:fa:c3:4e (SSID='Veldscholte' freq=2472 MHz)
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: Trying to associate with 54:e6:fc:fa:c3:4e (SSID='Veldscholte' freq=2472 MHz)
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: Associated with 54:e6:fc:fa:c3:4e
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=NL
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-STARTED EAP authentication started
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=52 -> NAK
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='redacted'
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='redacted'
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=54:e6:fc:fa:c3:4e reason=3 locally_generated=1
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: SME: Trying to authenticate with 54:e6:fc:fa:c3:4e (SSID='Veldscholte' freq=2472 MHz)
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: Trying to associate with 54:e6:fc:fa:c3:4e (SSID='Veldscholte' freq=2472 MHz)
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: Associated with 54:e6:fc:fa:c3:4e
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=NL
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-STARTED EAP authentication started
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=52 -> NAK
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='redacted'
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='redacted'
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=54:e6:fc:fa:c3:4e reason=3 locally_generated=1
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: SME: Trying to authenticate with 54:e6:fc:fa:c3:4e (SSID='Veldscholte' freq=2472 MHz)
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: Trying to associate with 54:e6:fc:fa:c3:4e (SSID='Veldscholte' freq=2472 MHz)
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: Associated with 54:e6:fc:fa:c3:4e
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=NL
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-STARTED EAP authentication started
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=52 -> NAK
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='redacted'
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='redacted'
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: l2_packet_send - sendto: Message too long
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=54:e6:fc:fa:c3:4e reason=3 locally_generated=1
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: SME: Trying to authenticate with 54:e6:fc:fa:c3:4e (SSID='Veldscholte' freq=2472 MHz)
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: Trying to associate with 54:e6:fc:fa:c3:4e (SSID='Veldscholte' freq=2472 MHz)
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: Associated with 54:e6:fc:fa:c3:4e
aug 07 23:55:40 LARS-SURKESH wpa_supplicant[732]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=NL
aug 07 23:56:02 LARS-SURKESH NetworkManager[473]: <warn>  (wlp3s0): Activation: (wifi) association took too long
aug 07 23:56:02 LARS-SURKESH kernel: wlp3s0: deauthenticating from 54:e6:fc:fa:c3:4e by local choice (Reason: 3=DEAUTH_LEAVING)                                                                                                                                                
aug 07 23:56:02 LARS-SURKESH NetworkManager[473]: <info>  (wlp3s0): device state change: config -> failed (reason 'no-secrets') [50 120 7]                                                                                                                                     
aug 07 23:56:02 LARS-SURKESH NetworkManager[473]: <info>  NetworkManager state is now DISCONNECTED                                                                                                                                                                             
aug 07 23:56:02 LARS-SURKESH NetworkManager[473]: <warn>  (wlp3s0): Activation: failed for connection 'Veldscholte'                                                                                                                                                            
aug 07 23:56:02 LARS-SURKESH NetworkManager[473]: <info>  (wlp3s0): device state change: failed -> disconnected (reason 'none') [120 30 0]                                                                                                                                     
aug 07 23:56:02 LARS-SURKESH kdeinit5[1126]: Calling notify on "Popup"                                                                                                                                                                                                         
aug 07 23:56:02 LARS-SURKESH kdeinit5[1126]: Calling notify on "Popup"                                                                                                                                                                                                         
aug 07 23:56:02 LARS-SURKESH kernel: cfg80211: Calling CRDA to update world regulatory domain                                                                                                                                                                                  
aug 07 23:56:02 LARS-SURKESH NetworkManager[473]: <warn>  Connection disconnected (reason -3)                                                                                                                                                                                  
aug 07 23:56:02 LARS-SURKESH NetworkManager[473]: <info>  (wlp3s0): supplicant interface state: associated -> disconnected                                                                                                                                                     
aug 07 23:56:02 LARS-SURKESH kdeconnectd[1172]: "Method \"GetAll\" with signature \"s\" on interface \"org.freedesktop.DBus.Properties\" doesn't exist\n"                                                                                                                      
aug 07 23:56:02 LARS-SURKESH kdeconnectd[1172]: kdeconnect.core: "Veldscholte"  state changed to  QFlags(0x2|0x4)                                                                                                                                                              
aug 07 23:56:02 LARS-SURKESH kdeconnectd[1172]: kdeconnect.core: Online status:  offline                                                                                                                                                                                       
aug 07 23:56:02 LARS-SURKESH kdeconnectd[1172]: kdeconnect.core: Sending onNetworkChange to  1  LinkProviders                                                                                                                                                                  
aug 07 23:56:02 LARS-SURKESH kdeconnectd[1172]: kdeconnect.core: Sending identity packet                                                                                                                                                                                       
aug 07 23:56:02 LARS-SURKESH NetworkManager[473]: <warn>  Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect.

And this goes on and on until NetworkManager gives up.

I also noticed that after I rmmod and modprobe the iwlwifi module, I can connect again.

I'm on Linux 4.1.4-1-ck but the stock kernel has this issue as well.

This problems sounds very similar to http://www.datahugger.de/2014/11/networ … -too-long/ but disabling power safe mode does not solve the problem.

Last edited by Compizfox (2015-08-07 22:20:50)

Offline

#2 2015-08-07 22:17:43

Compizfox
Member
Registered: 2015-08-06
Posts: 20

Re: WPA2 Enterprise (EAP) issues with Thinkpad W540

I found some additional error messages from wpa_supplicant:

wpa_supplicant[732]: l2_packet_send - sendto: Message too long

Unfortunately, Googling this error doesn't yield any results.

I'll update the error log in my OP with the complete sequence of messages.

Last edited by Compizfox (2015-08-07 22:29:50)

Offline

#3 2015-08-12 15:22:11

Compizfox
Member
Registered: 2015-08-06
Posts: 20

Re: WPA2 Enterprise (EAP) issues with Thinkpad W540

I just confirmed that I don't have this issue with WPA2-PSK networks. It seems to be specific to EAP / WPA2-Enterprise.

Offline

#4 2015-08-13 15:34:08

Compizfox
Member
Registered: 2015-08-06
Posts: 20

Re: WPA2 Enterprise (EAP) issues with Thinkpad W540

I think a kernel update (Linux 4.1.5-1-ck) fixed the issue!

Nevermind, it didn't sad

My current workaround for this is to have a systemd service that automatically rmmods en modprobes the iwlwifi module at resume, which works reasonably well.

Last edited by Compizfox (2015-08-13 18:05:55)

Offline

Pages: 1

Board footer

Powered by FluxBB