NetworkManager cannot connect to a wireless network with WPA2-Enterprise

Hello,
From some days ago, I cannot connect my laptop to my university’s network.
The network configuration is as follows:
Security: WPA2-Enterprise
Authentication: EAP-TTLS
Inner authentication: PAP
Data encryption: WPA2-AES

I can see the network in the list, but when I try to connect to it, the NetworkManager just ask the network data over and over again. I have no problem with other networks, and it works perfectly on Windows.

I use OpenSuse 12.3.

The /var/log/NetworkManager logs when I try to connect:


2013-10-28T21:12:23.293156+01:00 coegho-portatil NetworkManager[17762]: <info> Config: added 'ssid' value 'wifiusc'
2013-10-28T21:12:23.294165+01:00 coegho-portatil NetworkManager[17762]: <info> Config: added 'key_mgmt' value 'WPA-EAP'
2013-10-28T21:12:23.294627+01:00 coegho-portatil NetworkManager[17762]: <info> Config: added 'eap' value 'TTLS PEAP TLS'
2013-10-28T21:12:23.295080+01:00 coegho-portatil NetworkManager[17762]: <info> Config: added 'identity' value '<omitted>'
2013-10-28T21:12:23.295177+01:00 coegho-portatil NetworkManager[17762]: <info> Config: added 'ca_cert' value 'probe://'
2013-10-28T21:12:23.295424+01:00 coegho-portatil NetworkManager[17762]: <info> Config: added 'password' value '<omitted>'
2013-10-28T21:12:23.295699+01:00 coegho-portatil NetworkManager[17762]: <info> Config: set interface ap_scan to 1
2013-10-28T21:12:23.310032+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: disconnected -> scanning
2013-10-28T21:12:24.247975+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: scanning -> authenticating
2013-10-28T21:12:24.265185+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: authenticating -> associating
2013-10-28T21:12:24.278026+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: associating -> associated
2013-10-28T21:12:27.357208+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: associated -> disconnected
2013-10-28T21:12:28.367418+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: disconnected -> scanning
2013-10-28T21:12:29.304307+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: scanning -> authenticating
2013-10-28T21:12:29.310739+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: authenticating -> associating
2013-10-28T21:12:29.520899+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: associating -> associated
2013-10-28T21:12:32.829861+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: associated -> disconnected
2013-10-28T21:12:37.840275+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: disconnected -> scanning
2013-10-28T21:12:38.779693+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: scanning -> authenticating
2013-10-28T21:12:38.787022+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: authenticating -> associating
2013-10-28T21:12:38.792650+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: associating -> associated
2013-10-28T21:12:41.872273+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: associated -> disconnected
2013-10-28T21:12:46.882496+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: disconnected -> scanning
2013-10-28T21:12:47.817220+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: scanning -> authenticating
2013-10-28T21:12:47.829412+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: authenticating -> associating
2013-10-28T21:12:47.837791+01:00 coegho-portatil NetworkManager[17762]: <info> (wlan0): supplicant interface state: associating -> associated

/var/log/wpa_supplicant.log:


SME: Trying to authenticate with 00:1a:1e:6a:d0:70 (SSID='wifiusc' freq=2437 MHz)
wlan0: Trying to associate with 00:1a:1e:6a:d0:70 (SSID='wifiusc' freq=2437 MHz)
wlan0: Associated with 00:1a:1e:6a:d0:70
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wlan0: Authentication with 00:1a:1e:6a:d0:70 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: SME: Trying to authenticate with d8:c7:c8:34:79:61 (SSID='wifiusc' freq=2462 MHz)
wlan0: Trying to associate with d8:c7:c8:34:79:61 (SSID='wifiusc' freq=2462 MHz)
wlan0: Associated with d8:c7:c8:34:79:61
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wlan0: Authentication with d8:c7:c8:34:79:61 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: SME: Trying to authenticate with d8:c7:c8:34:73:61 (SSID='wifiusc' freq=2437 MHz)
wlan0: Trying to associate with d8:c7:c8:34:73:61 (SSID='wifiusc' freq=2437 MHz)
wlan0: Associated with d8:c7:c8:34:73:61
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wlan0: Authentication with d8:c7:c8:34:73:61 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: SME: Trying to authenticate with d8:c7:c8:34:6f:a1 (SSID='wifiusc' freq=2412 MHz)
wlan0: Trying to associate with d8:c7:c8:34:6f:a1 (SSID='wifiusc' freq=2412 MHz)
wlan0: Associated with d8:c7:c8:34:6f:a1
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wlan0: Authentication with d8:c7:c8:34:6f:a1 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: SME: Trying to authenticate with d8:c7:c8:34:79:21 (SSID='wifiusc' freq=2412 MHz)
wlan0: SME: Trying to authenticate with 00:0b:86:a6:62:c0 (SSID='wifiusc' freq=2412 MHz)
wlan0: Trying to associate with 00:0b:86:a6:62:c0 (SSID='wifiusc' freq=2412 MHz)
wlan0: Associated with 00:0b:86:a6:62:c0
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wlan0: Authentication with 00:0b:86:a6:62:c0 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: SME: Trying to authenticate with 00:0b:86:a5:f3:10 (SSID='wifiusc' freq=2462 MHz)
wlan0: Trying to associate with 00:0b:86:a5:f3:10 (SSID='wifiusc' freq=2462 MHz)
wlan0: Associated with 00:0b:86:a5:f3:10
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wlan0: Authentication with 00:0b:86:a5:f3:10 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: SME: Trying to authenticate with 00:0b:86:a5:eb:90 (SSID='wifiusc' freq=2462 MHz)
wlan0: SME: Trying to authenticate with 00:0b:86:a7:7e:50 (SSID='wifiusc' freq=2462 MHz)
wlan0: Trying to associate with 00:0b:86:a7:7e:50 (SSID='wifiusc' freq=2462 MHz)
wlan0: Associated with 00:0b:86:a7:7e:50
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wlan0: Authentication with 00:0b:86:a7:7e:50 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: SME: Trying to authenticate with 00:0b:86:a5:f5:d0 (SSID='wifiusc' freq=2412 MHz)
wlan0: SME: Trying to authenticate with 00:1a:1e:6a:d0:70 (SSID='wifiusc' freq=2437 MHz)
wlan0: Trying to associate with 00:1a:1e:6a:d0:70 (SSID='wifiusc' freq=2437 MHz)
wlan0: Associated with 00:1a:1e:6a:d0:70
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wlan0: Authentication with 00:1a:1e:6a:d0:70 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: SME: Trying to authenticate with d8:c7:c8:34:79:61 (SSID='wifiusc' freq=2462 MHz)
wlan0: Trying to associate with d8:c7:c8:34:79:61 (SSID='wifiusc' freq=2462 MHz)
wlan0: Associated with d8:c7:c8:34:79:61
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wlan0: Authentication with d8:c7:c8:34:79:61 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: SME: Trying to authenticate with d8:c7:c8:34:73:61 (SSID='wifiusc' freq=2437 MHz)
wlan0: Trying to associate with d8:c7:c8:34:73:61 (SSID='wifiusc' freq=2437 MHz)
wlan0: Associated with d8:c7:c8:34:73:61
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wlan0: Authentication with d8:c7:c8:34:73:61 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: SME: Trying to authenticate with d8:c7:c8:34:6f:a1 (SSID='wifiusc' freq=2412 MHz)
wlan0: Trying to associate with d8:c7:c8:34:6f:a1 (SSID='wifiusc' freq=2412 MHz)
wlan0: Associated with d8:c7:c8:34:6f:a1
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wlan0: Authentication with d8:c7:c8:34:6f:a1 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
wlan0: SME: Trying to authenticate with 00:0b:86:a6:62:c0 (SSID='wifiusc' freq=2412 MHz)
wlan0: Trying to associate with 00:0b:86:a6:62:c0 (SSID='wifiusc' freq=2412 MHz)
wlan0: Associated with 00:0b:86:a6:62:c0
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3

Any idea? I know some people asked similar questions before, but their posts are old (one or two years), and they didn’t recieve any answer useful to me.

Thank you very much for your help, and sorry for my english, it’s not my first language.

On Mon, 28 Oct 2013 20:46:02 +0000, coegho wrote:

> wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
> wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
> wlan0: Authentication with d8:c7:c8:34:79:61 timed out.

These three messages are repeated several times, so that would imply to
me either the authentication source isn’t responding, or the credentials
are incorrect. I would start by checking those items.

Jim

Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

Credentials are correct, I cheked it.
How can I check the authentication source? I know more people with the same problem, but some other people haven’t it.

@coegho,

did you try a connection using Security: WPA2-Personal?

No, I have no access to any router with WPA2-Personal security. And NetworkManager has not that option with this network (I use Gnome).
But WPA networks work fine.

I contacted the university and they told me that they see a lot of authentication errors with my MAC address, but the credentials are OK and I have no problems on Windows…

On 10/30/2013 01:36 PM, coegho wrote:
>
> keellambert;2594250 Wrote:
>> @coegho,
>>
>> did you try a connection using Security: WPA2-Personal?
>
> No, I have no access to any router with WPA2-Personal security. And
> NetworkManager has not that option with this network (I use Gnome).
> But WPA networks work fine.
>
> I contacted the university and they told me that they see a lot of
> authentication errors with my MAC address, but the credentials are OK
> and I have no problems on Windows…

To me, those authentication errors indicate that you do not have the
WPA2-Enterprise connection set up correctly; however, I do not know what might
be wrong. There must be another Linux user at the university that uses NM.
Compare your setup with theirs.

Finally I fixed this by myself. I turned to KDE, and now the wifi works. It seems to be a problem with the NetworkManager plugin from Gnome.
Thank you very much! You have answered me very quickly.

I am using NetworkManager + KDE, yet I am facing issue of authentication failure.
I even tried wpa_gui.
I cannot change from Enterprise to Personal.

Initially I thought that may be I need to supply CA.
But, when I try from Mac or Windows or Ubuntu I am able to connect, without need of CA.

Do we have any other application in KDE which we can use to connect to wifi network ?

On 12/03/2013 10:36 AM, mrsonu wrote:
>
> I am using NetworkManager + KDE, yet I am facing issue of authentication
> failure.
> I even tried wpa_gui.
> I cannot change from Enterprise to Personal.
>
> Initially I thought that may be I need to supply CA.
> But, when I try from Mac or Windows or Ubuntu I am able to connect,
> without need of CA.
>
> Do we have any other application in KDE which we can use to connect to
> wifi network ?

What version of openSUSE are you using. Please do not post without giving that
information.

WPA2 personnel does not need a certificate. That is needed for enterprise only.

NM works fine once it is configured properly. Use the applet to create the
connection. How to do that requires knowing the openSUSE version.

@lwfinger

Thanks for trying to help.

I have opensuse 12.3 and am trying to connect to a WPA2 Enterprise network.

I could get it working from Mac Osx without supplying any CA.

On 12/04/2013 10:06 AM, mrsonu wrote:
>
> @lwfinger
>
> Thanks for trying to help.
>
> I have opensuse 12.3 and am trying to connect to a WPA2 Enterprise
> network.
>
> I could get it working from Mac Osx without supplying any CA.

Your previous posting said the you were trying to change from Enterprise to
Personal, which was the basis of my answer.

Enterprise does not necessarily need a certificate; however, only Enterprise
will need it.

You say that you can connect with Ubuntu. What do you do there?