Version: (using KDE KDE 3.5.5) Installed from: Ubuntu Packages The K Network manager gui needs a change so that you can specify a WEP network with PEAP. This is possible with the Gnome network manager gui, but not knetworkmanager. It seems after selecting WPA enterprise we need a dropdown to change the key type to dynamic WEP. Here are the steps to connect to this type of network in GNOME. Hope this helps. 1.click the network-manager icon 2.select Connect to Other Wireless Network.. 3.changeWireless Security toWPA Enterprise This expands the menu to have more options 4.type network name, example: twdata 5.change EAP method to PEAP 6.change Key Type to Dynamic WEP 7.type user id in Identity, example: naustin 8.type user password in Password, example: turkey 9.Then connect. Thanks!!!
Created attachment 20783 [details] Add Key Type option in WPA Enterprise dialog This patch adds an Key Type option in WPA Enterprise dialog in order to enable PEAP authentication with Dynamic WEP. Tested on Kubuntu 7.04.
To build the patch I just added on (K)ubuntu 7.04 do the following: $ sudo apt-get install build-essential $ sudo apt-get build-dep knetworkmanager $ apt-get source knetworkmanager change into knetworkmanager directory and apply patch $ patch -p1 < path_to_patch The following steps are necessary since there is a problem with the Makefiles in the Ubuntu source package $ automake $ perl admin/am_edit Then as usual: $ ./configure $ make install Have fun! Matthias
There are other key types missing as well: TKIP and AES-CCMP Both are available by nm-applet, but not by knetworkmanager. Please add them!
Just checked, the patch includes the other methods as well, am I right? I submitted the patch at the Novell.com bugzilla as well: http://bugzilla.novell.com/show_bug.cgi?id=292728
this is a duplicate of Bug 143526 (or maybe the other one is?)
Please test against the newest SVN version. The latest commits (5 days ago) added support for key management to knetworkmanager.
This bug should be closed.
Fixed in KNM 0.2
*** Bug 141542 has been marked as a duplicate of this bug. ***