Bug 494262

Unfortunately, the NM plasmoid just chokes on most forms of encryption at the moment. This is known. We aren't using it by default for a reason.

We should keep this bug report open to track the issue though.

fwiw, wep works for me.  Haven't tried anything else myself.

Thanks for the info Kevin
Thanks for the tip Rex.

Hasan

There hasn't been any upstream work that would fix encryption that I can see since the snapshot that's in the repos. There are some convenience fixes that I can see, but nothing as to actual behavior change with wireless. I should be able to spin a new snapshot this week.

I appreciate your efforts a lot Ben.

Would it help to get involved directly with KDE (or vote at KDE Bugzilla)?

Hasan

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Problem exists in Fedora 11 distribution.  knetworkmanager (which worked in F10) has been replaced with this applet (which doesn't work).

I've successfully tested both WPA-PSK and WPA-EAP with the latest 2 snapshots in updates (and there's another one in testing now).

One caveat is that WPA-PSK needs the ASCII passphrase, the hex key didn't work for me.

Thanks for the comment.  I just installed F11 and applied the latest maintenance.  I am supplying the ASCII passphrase - but notice I get continually asked for the passphrase.  Maybe this is a kdewallet integration issue?  Here is the current software levels:

NetworkManager-openvpn-0.7.0.99-1.fc11.x86_64
NetworkManager-glib-0.7.1-4.git20090414.fc11.x86_64
NetworkManager-devel-0.7.1-4.git20090414.fc11.x86_64
NetworkManager-pptp-0.7.0.99-1.fc11.x86_64
NetworkManager-glib-devel-0.7.1-4.git20090414.fc11.x86_64
NetworkManager-vpnc-0.7.0.99-1.fc11.x86_64
NetworkManager-0.7.1-4.git20090414.fc11.x86_64
NetworkManager-gnome-0.7.1-4.git20090414.fc11.x86_64
kde-plasma-networkmanagement-0.1-0.11.20090504svn.fc11.x86_64

Gnome is working fine with NetworkManager so I know I'm entering the correct passphrase.

*** Bug 505292 has been marked as a duplicate of this bug. ***

WEP works fine, but wpa/wpa2 fails as described above.
(And works fine with nm-applet)

using this version it still fails:
kde-plasma-networkmanagement-0.1-0.12.20090519svn.fc11.x86_64

Apparently this plasma works fine with Kubuntu, so I would suspect that this is a specific fedora issue, or perhaps Kubuntu already has the necessary patches applied to it?

Some people (including me) have WPA working on F10, so I think this is just Kubuntu using older versions of some related software (NM? wpa_supplicant? kernel? something else? So far my downgrade attempts (NM and wpa_supplicant) have been shots in the dark).

I think this is correct that the newer version of network-manager is not compatible with kde-plasma-networkmanagement as I even tried an svn checkout and build and had the same issues.

So effectively it's broken for the time being for wpa :-(

Let's start by recapitulating that my attempted scratch builds of old NetworkManager and wpa_supplicant seem not to fix this issue.

JKnife on #fedora-kde made a seemingly naive "shot in the dark" type remark which actually turned out to make sense. His question was: "could it be D-Bus?" Well, it turns out it can:
* F10 has dbus-1.2.4-2.fc10, a permissive version,
* F11 has dbus-1.2.12-1.fc11, a version with strict security policies,
* the strict security policies have been known to cause problems with the old KDE 3 knetworkmanager,
so it's pretty much plausible that D-Bus may be at fault here as well. (As for why I'm saing his remark was a shot in the dark: his next question was what could have possibly changed in D-Bus... ;-) )

Expect a scratch build for a permissive version of D-Bus for F11 to try out from me ASAP.

(I forgot to mention in my recapitulation that the exact same snapshot of kde-plasma-networkmanagement on the exact same hardware has been reported to work on F10 but not F11.)

dbus-1.2.4.6permissive-1 scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=1460536

Please try this, 1. checking whether it fixes it and 2. reporting any logged errors from D-Bus (/var/log/messages) (especially if it does fix it).

(You should do a full reboot after the downgrade to make sure the system bus and all session buses get restarted.)

tried it, including reboot. Didn't make a difference for me. Not sure if if makes a difference that I try with a network that has hidden ESSID? Can connect with knetwormanager (kde3) just fine - same NetworkManager etc.


NetworkManager: <info>  Activation (wlan0/wireless): connection 'mytest' has security, and secrets exist.  No new secrets needed.
NetworkManager: <info>  Config: added 'ssid' value 'mytest'
NetworkManager: <info>  Config: added 'scan_ssid' value '1'
NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
NetworkManager: <info>  Config: added 'auth_alg' value 'OPEN'
NetworkManager: <info>  Config: added 'psk' value '<omitted>'
NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
NetworkManager: <info>  Config: set interface ap_scan to 1
NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated
kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> disconnected
NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associated
NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> disconnected
NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associated
NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> disconnected
NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associated
NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> disconnected
NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
NetworkManager: <info>  wlan0: link timed out.
NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associated
NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
NetworkManager: <info>  Activation (wlan0/wireless): association took too long.


normal would have been:
NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake                                     
NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> group handshake                                
NetworkManager: <info>  (wlan0): supplicant connection state:  group handshake -> completed

JKnife also reported that the D-Bus downgrade didn't help. So it's apparently not D-Bus either. So what is it? :-(

what I found out so far is that on a non-working connection using the plasmoid I get:

NetworkManager: <info>  Config: added 'ssid' value 'mytest'                                                                   
NetworkManager: <info>  Config: added 'scan_ssid' value '1'                                                                      
NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'                                                                 
NetworkManager: <info>  Config: added 'auth_alg' value 'OPEN'                                                                    
NetworkManager: <info>  Config: added 'psk' value '<omitted>'   


but with a working knetworkmanager (kde3) it logs:

NetworkManager: <info>  Config: added 'ssid' value 'mytest'                                                                   
NetworkManager: <info>  Config: added 'scan_ssid' value '1'                                                                      
NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'                                                                 
NetworkManager: <info>  Config: added 'psk' value '<omitted>'                                                                    
NetworkManager: <info>  Config: added 'pairwise' value 'TKIP CCMP'                                                               
NetworkManager: <info>  Config: added 'group' value 'TKIP CCMP'

is there any current development for fedora?

kde marks this to be closed:
https://bugs.kde.org/show_bug.cgi?id=195824

We have a new snapshot with a monolithic KDE 4 knetworkmanager and an experimental plasmoid (now split into plasmoid and kded4 service) in updates-testing now. It works for some people, but apparently not for others, see bug 521467.

kde-plasma-networkmanager doesn't allow me to connect to any wireless network,

Sep 24 01:02:53 NetworkManager: <WARN>  connection_get_settings_cb(): connection_get_settings_cb: Invalid connection: 'NMSettingConnection' / 'id' invalid: 1
Sep 24 01:02:59  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

However nm-applet connects fine but with some difficuilty, I really wanted to use knetworkmanager since it work fine in fedora 10 and I'm sad it's not included in fedora 11.

Then for the moment try installing the knetworkmanager from F10 (kde3). You might need to downgrade to an NetworkManager 0.7.x however ... Worked here for the moment.

There's also a KDE 4 knetworkmanager in updates-testing.

but that one lacks features over the kde3-version. e.g. it doesn't connect to WPA2-networks for me. And it doesn't support hidden networks (no option to select where to connect - instead the KDE4-plasmoid has that option but doesn't connect etc.) :-(

kde-plasma-networkmanagement-0.9-0.3.20090930svn.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/kde-plasma-networkmanagement-0.9-0.3.20090930svn.fc11

Just an FYI; going from '4-way handshake' -> 'disconnected' status usually means the PSK is wrong.  Could be a problem with hashing the WPA PSK to the hex format in the plasmoid?  I'd try entering the passphrase in hex format if you can, you can get it from wpa_passphrase manually like so:

[dcbw@localhost ~]$ wpa_passphrase my_ssid
# reading passphrase from stdin
foobar37
<hit return after typing your passphrase>
network={
	ssid="my_ssid"
	#psk="foobar37"
	psk=dfc6955eb3626193b525cbd3aebd886f3a21afa1ea27901a9327f77a166b1ae1
}

then use all the hex digits there instead of your passphrase when setting up the network configuration.

This will test whether the hashing that the plasmoid uses is correct.  If you get connected using the hex PSK, then the hashing in the plasmoid is somehow buggy.

Except it won't work... The plasmoid doesn't accept hex PSKs.
https://bugs.kde.org/show_bug.cgi?id=191879
(That bug got fixed on July 26, but that's already the new, refactored codebase. What we ship is from 20090519.)

So we figured out this is likely a case of -O2 optimization during compile along with ignored strict aliasing warnings in the sha1.c code.  Fix should be forthcoming.

        } CHAR64LONG16;
        CHAR64LONG16* block;
 #ifdef SHA1HANDSOFF
-       u32 workspace[16];
+       unsigned char workspace[64];
        block = (CHAR64LONG16 *) workspace;
        memcpy(block, buffer, 64);
 #else

kde-plasma-networkmanagement-0.9-0.3.20090930svn.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.

This system has: knetworkmanager-0.9-0.3.20090930svn.fc11.i586

I log in, try to connect wpa2 protected visible AP with password, it always fails.

Killing the knetworkmanager process and running command:

$ cnetworkmanager --wpa-pass=cafevstallinn -C "Cafe VS avalik"
Entering mainloop
(18:33:29) State: CONNECTING
(18:33:41) State: CONNECTED

and connection succeeds. ThinkPad x200s, 5100AGN wifi.

This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

I think this has been fixed already, at least it works here.

Juha, mind sharing what versions of NetworkManager and kde-plasma-networkmanagement you tested?

currently i've 0.9-0.12.20100220.fc11.i586 installed, haven't tried it recently so it might have been some earlier that started working.

Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.