Network Manager Plasmoid won't connect to "WPA Enterprise" AP's in Jaunty

This is a partial dup of 330811, but that defect only refers to the hidden SSID aspect. One of the networks that i'm having trouble with broadcasts ESSID.

I should also mention that 325252 might also be relevant, given that the non-hidden network (essid=tamulink-wpa) uses both AES and TKIP (as the user sees fit.)

I too am experiencing this same problem. I connect to WPA-PSK, WEP and Open/Public networks just fine. When I select my Companies network from the Plasma List or even manually try to configure it it says "Connecting to <network_name>" but then does nothing at all...I use WPA-Enterprise PEAP/MSCHAPv2 through steel-belted RADIUS. Had no problems whatsoever with it in Intrepid. I have updated just about everything I can and still no resolution. I have checked all my logs, but since it never actually makes an effort to connect, it does not show in any of them. Is this an issue across the board with Jaunty or are others able to connect via WPA-Enterprise?

I confirm the problem here. I'm no able to connect to my AP at work (using WPA enterprise PEAP/MSChap v2) with KDE network manager plasmoid. My AP is broadcasting its ESSID.

However, connection works fine with WPA/WPA2 personal APs.

Connection works fine on gnome with gnome network manager applet.

> cat /var/log/daemon.log

NetworkManager: <WARN> wait_for_connection_expired(): connection (2) /org/freedesktop/NetworkManagerSettings/1 failed to activate (timedout): (0) Connection was not provided by any settings service.

looks like it is not even trying to connect to the AP because I have nothing in wpa_supplicant log.

After the latest updates from 3/11/09 with NM and The latest Kernel I still cannot connect to WPA Enterprise using PEAP/MSCHAPv2 over 802.1x. Here are the lines from /var/log/daemon.log:
ar 12 07:12:14 ced143601lin NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Mar 12 07:12:14 ced143601lin NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
I might add this is the only log file in which I been able to come up with anything. As I previously stated it doesn't even act like it is trying to connect.
Thanks all for your work! Jaunty looks awesome!

I can confirm it too.
https://bugs.launchpad.net/ubuntu/+source/plasma-widget-network-manager/+bug/325252/comments/3

One more addition from my daemon.log:

Mar 16 05:26:50 ced143601lin NetworkManager: <WARN> connection_get_settings_cb(): connection_get_settings_cb: Invalid connection: 'NMSetting8021x' / 'phase1-peaplabel' invalid: 1
Mar 16 05:26:56 ced143601lin NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/4 failed to activate (timeout): (0) Connection was not provided by any settings service
Thanks!

I don't know if it helps, but I'm having connection problems with EAP network as well. Both plain wpa_supplicant and network-manager-gnome (nm_applet) work fine. This is de wpa_supplicant.conf part that makes wpa_supplicant tick:

network={
        ssid="ru-wlan" #(Visible)
        key_mgmt=WPA-EAP
        eap=TTLS
        phase2="auth=PAP"
        identity="***"
        password="***"
}

I also see the wait_for_connection_expired() in daemon.log

I have tested this today on up-to-date Kubuntu/Jaunty. I used hidden network with following settings:
- WPA Enterprise,
- PEAP,
- MSCHAPv2

nm-applet 0.7.1~rc3-0ubuntu1: works!
knetworkmanager 1:0.7svn864988-0ubuntu8: works!
plasma-widget-network-manager 0.0+svn930811-0ubuntu2: does not even try to connect

I think that knetworkmanager task should be closed as Fixed, while there is for sure the problem with plasma-widget. I think when you add hidden network (Manage connections -> Add) and mark it to "Autoconnect", it does not even try to auto-connect and also does not show newly added network in the list of available SSIDs.

See attached syslog file - search for "==> TRY" to see different clients used.

I think the root cause is linked to this messages from syslog:

Mar 18 15:09:47 lure NetworkManager: <WARN> list_connections_cb(): Couldn't retriev
e connections: No such method 'ListConnections' in interface 'org.freedesktop.Networ
kManagerSettings' at object path '/org/freedesktop/NetworkManagerSettings' (signatur
e '').
Mar 18 15:10:01 lure /USR/SBIN/CRON[5737]: (root) CMD ([ -x /usr/sbin/update-motd ]
&& /usr/sbin/update-motd 2>/dev/null)
Mar 18 15:11:01 lure NetworkManager: <WARN> connection_get_settings_cb(): connectio
n_get_settings_cb: Invalid connection: 'NMSetting8021x' / 'phase1-peaplabel' invalid
: 1

More info about my system:
HW: Lenovo x200s, Intel 5300 WiFi
SW: network-manager 0.7.1~rc3-0ubuntu2

The knetworkmanager task is the upstream bug link, by the way.

I've created a patch which don't set the peaplabel setting when using peap version 0 and also don't set it when not configured (which currently is not possible using the GUI).

I've patched plasma-widget-network-manager and uploaded it to my PPA.
It works for me when using WPA-EAP with PEAP and MSCHAPv2 but I haven't tested it with any other configuration.

What is your PPA address?
Or is this attachment your patch?
Regards

Details of how to use it here: https://launchpad.net/~hermansson-per/+archive/ppa

Does not work here, same setup, just that SSID is hidden - I think this is different problem actually.

The patch worked for me, I have successfully connected to my office network using WPA-EAP PEAP MSCHAPv2 802.1x RADIUS auth. Thanks for the work!

Per Hermansson, cheers.

Your patch allows me to successfully connect to the network at my school. I'll try it at work tomorrow, but I'll bet the "hidden SSID" issue with this plasmoid prevents that from working.

I confirm this bug - can't connect to Eduroam network:
- WPA Enterprice
- TTLS
- PAP

The knetworkmanager application from KDE4 works fine.

I can confirm this bug (Eduroam network, wpa enterprise/ttls/mschapv2). Can also confirm that it works with Per Hermanssons packages (Thanks Per!).

I've tried Per Hermanssons patch, but it doesn't seem to function for version 1 PEAP - in fact, it looks like it's hard-coding version 0. It seems to make a better attempt at connecting, but I get the following message in /var/log/daemon.log:

Apr 6 14:20:32 nightfall NetworkManager: <info> Config: added 'ssid' value 'WC_AP'
Apr 6 14:20:32 nightfall NetworkManager: <info> Config: added 'scan_ssid' value '1'
Apr 6 14:20:32 nightfall NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-EAP'
Apr 6 14:20:32 nightfall NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
Apr 6 14:20:32 nightfall NetworkManager: <info> Config: added 'password' value '<omitted>'
Apr 6 14:20:32 nightfall NetworkManager: <info> Config: added 'eap' value 'PEAP'
Apr 6 14:20:32 nightfall NetworkManager: <info> Config: added 'fragment_size' value '1300'
Apr 6 14:20:32 nightfall NetworkManager: <info> Config: added 'phase1' value 'peapver=0'
Apr 6 14:20:32 nightfall NetworkManager: <info> Config: added 'phase2' value 'autheap=MSCHAPV2'

Charles good catch!
I've found that the widget stores the PEAP version settings as a string ("one" and "zero") but tried to load it as numbers so the loading always failed and the default value 0 was always used.

I've created a patched and updated my PPA (version 0.0+svn930811-0ubuntu3~ppa2) but testing this is not easy for me so if anybody could confirm that the patch works for peap version 1 would be great.

Thanks for the fix, /var/log/daemon.txt now reports that version 1 is being set. Unfortunately, I'm still not able to connect!

Apr 7 08:49:22 nightfall NetworkManager: <info> Activation (wlan0/wireless): association took too long.
Apr 7 08:49:22 nightfall NetworkManager: <info> (wlan0): device state change: 5 -> 6
Apr 7 08:49:22 nightfall NetworkManager: <info> Activation (wlan0/wireless): asking for new secrets
Apr 7 08:49:23 nightfall NetworkManager: <WARN> get_secrets_cb(): Couldn't get connection secrets: User refused to supply secrets.
Apr 7 08:49:23 nightfall NetworkManager: <info> (wlan0): device state change: 6 -> 9
Apr 7 08:49:23 nightfall NetworkManager: <info> Activation (wlan0) failed for access point (WC_AP)
Apr 7 08:49:23 nightfall NetworkManager: <info> Marking connection 'WC_AP' invalid.
Apr 7 08:49:23 nightfall NetworkManager: <info> Activation (wlan0) failed.

I suspect that it's possible that our own system here is misconfigured (it takes a LONG time to connect), but the fact remains that I *can* connect with nm-applet.

So I went through and compared the log messages from the (unsuccessful) plasmoid attempt to connect vs. the (successful) nm-applet attempt to connect to PEAP. There were two differences (before connection failure) that I saw:

PLASMOID:
Apr 7 08:48:22 nightfall NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-EAP'
Apr 7 08:48:22 nightfall NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
Apr 7 08:48:22 nightfall NetworkManager: <info> Config: added 'phase2' value 'autheap=MSCHAPV2'

NM-APPLET:
Apr 7 09:39:47 nightfall NetworkManager: <info> Config: added 'key_mgmt' value 'IEEE8021X'
Apr 7 09:39:47 nightfall NetworkManager: <info> Config: added 'phase2' value 'auth=MSCHAPV2'

There were intervening lines, but they were the same for each configuration. So, perhaps networkmanager isn't recognizing 'autheap' or 'WPA-EAP', whereas it DOES regcognize 'auth' and 'IEEE8021X'?

I'm no expert on wireless security so perhaps someone else can answer on this but from looking at the man page of wpa_supplicant.conf (http://linux.die.net/man/5/wpa_supplicant.conf) and the knetworkmanager program there seems to be a difference between using security with WPA-EAP (as you do on plasmoid) and IEEE8021X (used on NM-APPLET).

I don't think there are any support in plasmoid to configure the connection to use IEEE8021X so that may be the reason why it doesn't work for you.

Thanks. For what it's worth, I've filed a new bug report (as this seems to be a different issue than this bug) under #357170.

Ok I had the same problem as everyone else.

Trying to connect to WPA-EAP with PEAP and MSCHAP v2 with CA cert etc. and it wouldn't work...

#tail -f /var/log/daemon.log
NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/1 failed to activate (timeout): (0) Connection was not provided by any
settings service

Added "deb http://ppa.launchpad.net/hermansson-per/ppa/ubuntu jaunty main" patch and upgraded and after reboot.

Connected perfectly fine!

Awesome thanks for the patch!

But if this works and fixes a bug so nicely why is it not in the official ubuntu updates repo? Or is this patch still going to be uploaded?

I have the same problem but found something else in my logfile:
Network manager connects to the wlan and tries to receive an IP from the DHCP server - this fails.
I only see DHCPDISCOVER loglines but no DHCPOFFER.

Using the same DHCP server with a network cable works out of the box. Also several other laptops
work smoothless with the same WLAN. Ubuntu 9.04 beta stopped working some time ago after on of the
updates (don't know which one exactly). After updating 8.10 to 9.04 it was still working correct,
so the problem must be introduced sometimes in the last weeks.

I confirm this bug.
After upgrading my system on 9.04 rc1 ... my WPA-EAP with TTLS and PAP connection stopped working. Previously, no problems with knetworkmanager.

I also tested the patch mentioned before (by hermansson). It neither worked (TTLS and PAP) for me. After updating the plasma-widget-network-manager from the given ppa, I wasn't even able to established a connection to an unencrypted network.

Hi, thanks for trying my fix with TTLS. In helping the troubleshooting can you provide parts of your /var/log/daemon.log log that shows all lines starting with NetworkManager when you try to connect.

Also can you tell a little bit about your wireless connection like if your are using certificates.

Hej, thanks for reply - sorry for my delayed answer, I wasn't able to test it yesterday.
Here the output of the daemon.log... it seems that the configuration isn't even stored correctly:

NetworkManager: <WARN> connection_get_settings_cb(): connection_get_settings_cb: Invalid connection: 'NMSetting8021x' / 'phase2-autheap' invalid: 1
NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/4 failed to activate (timeout): (0) Connection was not providedb by any settings service

Furthermore I also tested to connect with the xfce-networkmanager, to exclude driver-issues derived from madwifi. It works correctly.

Some additional information to the network:
- wpa-eap tunneled TLS (TTLS) with PAP
- no ca certificate
- anonymous identity: <email address hidden>
- identity: <email address hidden>
- <password>

bye a

I have to confirm this bug, too. I attached a certificate chain (.pem), but the message is the same as reported bei aweight.

This doesn't seem to be the same issue as match the comment, but seems to match the configuration of the original submitter:

I am not able to specify "LEAP" as an eap method, it's simply not offered. I'm attaching a screenshot of my (working) configuration in gnome's nm-applet.

Won't connect either here on a wpa-eap with ttls, tkip (no option at all?) and pap without any certificate.

It says: "connecting to xyz" but the tray icon does not show this shiny animation ;)

The patch from the ppa listed here does not work for my setup either.

Great news, both my patches has been commited upstream.
But no new news on the ttls issues yet.

I also have the TTLS issue. I am using TTLS, a CA certificate and PAP (for connecting to the eduroam network). This is my log:

May 4 11:34:36 [kernel] input: b43-phy0 as /devices/virtual/input/input6
May 4 11:34:37 [kernel] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
May 4 11:34:37 [kernel] Registered led device: b43-phy0::radio
May 4 11:34:37 [NetworkManager] <info> (wlan0): device state change: 2 -> 3_
May 4 11:34:37 [NetworkManager] <info> (wlan0): supplicant interface state: starting -> ready_
May 4 11:34:53 [NetworkManager] <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/5 failed to activate (timeout): (0) Connection was not provided by any settings service_

BTW: I have also tried the latest SVN code of the plasmoid - but it is still not working.

I've changed the properties that the application sends to Network Manager so WPA-EAP with TTLS should now work. Can anyone experience problems using TTLS try version ppa3 in my PPA and report if it works.

Also the changes also apply to WPA-EAP with PEAP so I would like if those who got PEAP to work with my previous versions also tested the new version to ensure it still works.

I'm attaching a debdiff over the changes I made.

And PEAP still isn't working with the intel 3945 controller. I don't know if this is a driver problem or a network manager problem. Does *anyone* use an intel 3945 with PEAP and the networkmanager plasmoid?

I testet your newest ppa version withWPA2 enterprise, TTLS and PAP and a certificate.

+the icon is showing an animation now
+tries to connect for about 1 minute

-connection times out

daemon.log enclosed

You're doing a great job. Thank you!

If using certificates, make sure you do not run into another issue, which is purely NetworkManagers fault. https://bugzilla.gnome.org/show_bug.cgi?id=594466

@Andreas Wenning
You said you were using WPA Enterprise/TTLS/PAP.

There is an anonymous Identity with a certificate. Did you leave this option blank? Or did you use System CA Certs?

@rabauke

A friend of mine is using Jaunty. The login works on that machine. I think he's using a similar version of NetworkManager concerning the issue you linked to?

@apo
No certificates used at all. CA certs field left blank; and use system CA certs not ticked.

I retried it today and it didn't work with certificate, without, or the System CA certs. I wonder what this msg from syslog means:

Sep 16 16:05:45 -laptop NetworkManager: <info> Config: added 'ca_cert' value 'blob://-org-freedesktop-NetworkManagerSettings-7-ca_cert'

This is not my certificate i added. It stays with this msg. Doesn't matter what i choose (my cert, system cert, none)
Full log enclosed.

I'm using Lucid and can't connect in Kubuntu, but Lucid Ubuntu works fine with the same settings.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/09/2010 01:28, molecule-eye wrote:
> I'm using Lucid and can't connect in Kubuntu, but Lucid Ubuntu works
> fine with the same settings.
what type of encryption you have to connect to?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEUEARECAAYFAkyD5ZkACgkQggfXXPAclJG8JgCXdMfKlX+ZAQuVqqUwSVKYskXl
bgCcD3o+lqVHlx6fTouM0U4TLUwAP18=
=zzFe
-----END PGP SIGNATURE-----