Bug 186325 - networkmanager plasmoid won't connect to WPA enterprise networks
Summary: networkmanager plasmoid won't connect to WPA enterprise networks
Status: RESOLVED DUPLICATE of bug 192597
Alias: None
Product: Network Management
Classification: Miscellaneous
Component: KDED Module (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-06 11:35 UTC by Chris
Modified: 2009-07-31 06:49 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
AP description (1.36 KB, text/plain)
2009-03-06 11:36 UTC, Chris
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris 2009-03-06 11:35:39 UTC
Version:           0.0+svn930811 (using Devel)
Compiler:          gcc 4.4.3 ubuntu
OS:                Linux
Installed from:    Compiled sources

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.
Comment 1 Chris 2009-03-06 11:36:13 UTC
Created attachment 31828 [details]
AP description
Comment 2 Chris 2009-03-06 11:38:09 UTC
Sorry, I could not set the package to plasma network manager while reporting the bug. I got a "A legal version was not set." from bugzilla. So I set the package to plasma.
Comment 3 Chris 2009-03-06 11:41:21 UTC
Several users reported the problem here: 
https://bugs.launchpad.net/ubuntu/+source/plasma-widget-network-manager/+bug/334052
Comment 4 Andrew Malota 2009-03-23 15:35:49 UTC
(In reply to comment #3)
> Several users reported the problem here: 
> https://bugs.launchpad.net/ubuntu/+source/plasma-widget-network-manager/+bug/334052

affects me too.
Comment 5 Andrew Malota 2009-03-26 20:18:37 UTC
A patch provided by Per Hermansson here:
http://launchpadlibrarian.net/24301956/phaselabel-fix.debdiff

(above is direct link to deb patch, see ubuntu bug https://bugs.launchpad.net/ubuntu/+source/plasma-widget-network-manager/+bug/334052 for full discussion.)

fixes the issue for me. I'm able to associate to enterprise AP's now.
Comment 6 Joel Goguen 2009-04-07 13:07:39 UTC
That link should be http://launchpadlibrarian.net/24909444/peapver-parsing.debdiff, it was updated to properly parse the PEAP version.
Comment 7 Dan 2009-05-04 11:45:44 UTC
TTLS with CA-certificate and PAP is still not working with the latest SVN code:

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_
Comment 8 Joel Goguen 2009-06-18 21:08:40 UTC
This also doesn't work for networks using TTLS/PAP with no certificate or anonymous identity, just a username and password.  Here are the only two lines output to /var/log/daemon.log from starting to connect until connection failed.  The exact same lines were output to /var/log/syslog.

Jun 18 15:56:25 hermes NetworkManager: <WARN>  connection_get_settings_cb():
connection_get_settings_cb: Invalid connection: 'NMSetting8021x' /
'phase2-autheap' invalid: 1
Jun 18 15:56:30 hermes NetworkManager: <WARN>  wait_for_connection_expired():
Connection (2) /org/freedesktop/NetworkManagerSettings/3 failed to activate
(timeout): (0) Connection was not provided by any settings service
Comment 9 Joel Goguen 2009-06-18 21:11:55 UTC
Forgot to mention, the version I'm using is from Kubuntu, version 0.0+svn966653-0ubuntu0.1 in the jaunty-proposed repository.
Comment 10 Will Stephenson 2009-07-31 06:49:36 UTC
This took a long time to triage correctly.

The "Connection was not provided by any settings service" just indicates that NM decided the connection was invalid - you can see this in Joel Gaguen's comment - phase2 auth_eap_ should not be used for TTLS as can be seen at http://hostap.epitest.fi/wpa_supplicant/ under "Supported EAP methods".

However the fix is more complex than Per's patch suggests - there are other ways auth is broken and I want to do it right.

*** This bug has been marked as a duplicate of bug 192597 ***