Version: 0.1-r2 (using KDE KDE 3.5.6) Installed from: Gentoo Packages Compiler: gcc 4.1.2 OS: Linux I need to connect to EAP based network running PEAP, but I can't enter all the details, as there is no way to specify the encryption type once EAP, PEAP are selected. I need to be able to choose TKIP.
Ditto... the only way that I can connect to my campus' wireless network is by using nm-applet, where I can specify the "Key Type" (protocol) TKIP. Auto doesn't work, I have to manually specify TKIP. It's highly unfortunate that the only way to do wireless is with a GNOME app... ;)
I confirm, knetworkmanager doesn't allow me to connect to our campus wireless network, because I can't specify TKIP. Using (K)Ubuntu Feisty Fawn (7.04).
confirm this bug as well, moreover, my network is WEP protected, and when i select it from the list it allows me to select only WEP configuration and not WPA
PS. i use Kubuntu system
*** This bug has been confirmed by popular vote. ***
Created attachment 21214 [details] knetworkmanager v0.2
fixed in KnetworkManager v0.2 (using in Kubuntu Gutsy)
it was not fixed. what your image show is already available in the 0.1 version. the problem is with authentication in WPA ENTERPRISE there is no way to select WEP protocol in that mode (personally i need Dynamic WEP) t
I have the same issue reported here: http://bugs.gentoo-xeffects.org/show_bug.cgi?id=11 This still exists in the source repo version as well. The issue is that when you select WPA Enterprise from the GUI, you are not provided the choice to select the WPA Protocol (TKIP, CCMP or Automatic). It appears to possibly default to CCMP or nothing at all (i.e. it doesn't seem to use automatic). This option is only available is you select WPA Personal. The issue with that is that you can then no longer use certificates that exist under the Enterprise option. This is a bug and needs to be addressed. Can this be re-assigned to the new current/active knetworkmanager maintainer if Will Stephenson is not the correct maintainer anymore? Thanks
i have another problem: when using tls eap i cannot insert the password for the identity (my network uses tls, mschapv2 second auth (but it doesn't really matter because it connects also without the second stage auth), identity, password for identity, ca cert, private cert and password for private key, and tkip (i think that it's wpa1). when setting tls i cannot chose the identity password. the gnome nm-applet works and connects because i can set all the options above.
is this bug connected to: http://bugs.kde.org/show_bug.cgi?id=145984
a solution is available here: http://bugs.kde.org/show_bug.cgi?id=138504
i wasn't able to apply that patch on the 0.2 version. and in the 0.2 it still lacks the support for chosing tkip and other key encryption methods. not telling of the things that knm doesn't accept all the settings that you need set (as i told you i need to set wpa1,tkip,username, username password, tls, mschapv2,ca cert, private key cert, private key password and when i chose tls i have the username password blocked from setting it). i've also talked with mr Roderick B. Greening a gentoo developer about that patch and he has also told me that the patch needs a lot of work to be converted and function with the 0.2 version, so i hoped that it would have been included inside the new release along with the above request: leave the username password setting enabled when setting tls mode. thanks.
Please check against the latest knetworkmanager version from svn. It looks like that keymanagement was added: http://websvn.kde.org/branches/extragear/kde3/network/knetworkmanager/src/knetworkmanager-encryption.cpp?r1=703269&r2=711598 If it works, please close this bug.
Fantastic! I'll check this out tomorrow. #!/jon On September 18, 2007, Roland Wolters wrote: [bugs.kde.org quoted mail]
I can't compile... g++ dies looking for a function called nl_cache_destroy_and_free(). What version of libnl does knetworkmanager require? I have Ubuntu's 1.0~pre6-5 installed.
the program compiles but doesn't start. it crashes whenever i try to start it.
i finally managed to get installed and to run the svn version, but still it hasn't tkip/ccmp version select and when selecting the tls there cannot be set the password, since the password module is disabled. see attached image.
Created attachment 21667 [details] knetworkmanager_0.2_svn_wpa_enterprise in the attachement you can see that the password cannot be set when using tls and that knm misses a way to expressivelly select tkip.
beso,was it possibly before to set the password using TLS? Besides, on my system I am able to select TKIP or AES-CCMP, see http://liquidat.wordpress.com/2007/09/20/knetworkmanager-with-tkipaes-ccmp-support-and-gnome-220/
[quote]beso,was it possibly before to set the password using TLS? [/quote] i don't really remember, but even it was not possible i still need to be able to use it in tls or otherwise i would not be able to connect to the network. maybe it's not a standard network cause mschapv2 cannot be used normally with tls and cause i think that the password maybe cannot be used with the certificate, but still my university network uses it and i'll need to be able to use it, as i am with the gnome nm-applet. i needed to uninstall the gentoo version to be able to see the svn version, and now the tkip option seems to be there. but as i said, it's useless if i cannot chose the password with the tls eap. thanks
The question now is if that is a regression. Anyway, about the TLS password thing: please fill a new bug report about it so that the different bugs are kept separated (and do get a proper title, btw.) This bug can now be closed.
Fixed in KNM 0.2
I still can't connect to a dynamic wep network (as said in comment #8) or has this become a seperate bug?