| Summary: | NetworkManager plasmoid fails to connect to WPA-EAP wireless networks | ||
|---|---|---|---|
| Product: | [Unmaintained] Network Management | Reporter: | Cyril Brosch <info> |
| Component: | Plasma Widget | Assignee: | Will Stephenson <wstephenson> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | andresbajotierra, dominik.tritscher, sebas |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | log of NetworkManager with 2 connections | ||
|
Description
Cyril Brosch
2009-04-29 15:52:44 UTC
TTLS or PEAP is definitely selectable. I know about the missing cipher selections. bnc#396347 is about knetworkmanager - Could you tell me your EAP network settings once more for the record - EAP metho: PEAP or TTLS (or both)? Inner auth: PAP or MSCHAPv2? I'm using TTLS+MSCHAPv2, without certificates successfully here. I can't reproduce the invalid path warning but I will update the NM-kde4 packages in KKFD to latest trunk in case it was fixed since last week. Sorry for the PEAP/TTLS, of course it's possible. For completing: I use NetworkManager-0.7.0.r4359, NetworkManager-kde4-0.7r958040. Here is a full list for my university's network: http://www.zedat.fu-berlin.de/Eduroam-unsupported - I tried both with TTLS and PEAP, with PAP and mschapv2. Certificates are needed for the connection, but I tried only the ones with .pem, should I try the .cer, too? I think the problem is not a detail of the encryption, it rather seems as the plasmoid doesn't even try to establish a connection (the icon doesn't change although I get the system message "connecting eduroam", and via plasmoidviewer I get that error message already after one second). What does the daemon's log say? See userbase.kde.org/NetworkManagement for how to find that. Created attachment 33244 [details]
log of NetworkManager with 2 connections
I just checked the log, the attachment contains a successful connection the the network (from 19th of march, so I must have changed something afterwards, but unfortunately I can't remember), and an unsuccessful from today. I can confirm this issue using svn build 966653 (from an ubuntu ppa package). Here is the relevant part of my daemon.log: May 27 10:19:29 thechief-laptop console-kit-daemon[3247]: WARNING: Couldn't read /proc/3246/environ: Failed to open file '/proc/3246/environ': No such file or directory May 27 10:19:50 thechief-laptop NetworkManager: <WARN> connection_get_settings_cb(): connection_get_settings_cb: Invalid connection: 'NMSetting8021x' / 'phase2-autheap' invalid: 1 May 27 10:19:50 thechief-laptop last message repeated 6 times May 27 10:24:00 thechief-laptop 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 May 27 10:24:54 thechief-laptop 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 May 27 10:28:08 thechief-laptop 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 I use a WPA-EAP connection with TTLS-PAP. The connection works fine using the gnome nm-applet. It used to work fine with svn930811. The problem remains in KDE 4.3 RC1. *** This bug has been marked as a duplicate of bug 192597 *** |