Bugzilla – Bug 382440
KNetworkManager ignores info from scanning in it's user interface
Last modified: 2008-06-18 15:55:37 UTC
There is part of my iwlist scan: Cell 04 - Address: 00:14:BF:77:9A:C2 ESSID:"linksys_zajec" Mode:Master Channel:8 Frequency:2.447 GHz (Channel 8) Quality=66/100 Signal level=-48 dBm Noise level=-71 dBm Encryption key:on IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s Extra:tsf=00000012bcf438dc
Created attachment 209682 [details] First window of connection configuration My network uses WPA but KNetworkManager allows connecting to this network right in this stage of configuration. This means trying to connect without giving key while we are sure that key is needed. Connection button should be deactivated when focusing network with encryption used.
Created attachment 209683 [details] Default view of second stage of configuration In this stage we configure security settings. My network uses WPA encryption but... KNetworkManager doesn't check "Use Wireless Security" by default. What is point of that? If we click "Next" we will skip typing key network and connection won't be succesfull.
Created attachment 209687 [details] View of second stage after checking obvious "Use Wireless Security" KNetoworkManager wants user to type all theses magic settings. This is something absolutly crazy as it SHOULD be done by KNetworkManager without even showing that to user. In some rare situations (when 2 different encryptions are available, ex. WPA1 and WPA2) there could be radio button. But that's all. Also there is magic "PSK" which for most of the users mean nothing.
Correct, this has to be improved. I'll try to fix that up for the next Beta.
(In reply to comment #3 from Rafał Miłecki) > KNetoworkManager wants user to type all theses magic settings. This is > something absolutly crazy as it SHOULD be done by KNetworkManager without even > showing that to user. In some rare situations (when 2 different encryptions are > available, ex. WPA1 and WPA2) there could be radio button. But that's all. That is done in Beta3.
Nice news, thanks Helmut for fixing that! Great you were able to fix that before 11.0 final.
Helmut: I updated my Beta 1 to current factory tree and I have: zajec@linux:~> rpm -qa | grep NetworkManager NetworkManager-gnome-0.7.0.r720-3 NetworkManager-glib-0.7.0.r3649-2 NetworkManager-0.7.0.r3649-2 NetworkManager-kde-0.7r805840-3 When I configure new wireless connection to my zajec_gorny network which is: Cell 01 - Address: 00:18:39:DD:EE:78 ESSID:"zajec_gorny" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=66/100 Signal level=-48 dBm Noise level=-71 dBm Encryption key:on IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s 48 Mb/s; 54 Mb/s Extra:tsf=000003e889e40644 KNetworkManager is second step has "Use Wireless Security" *unchecked*. I have to check this option manually and then I have to type key. It's even bigger mess with other Cell 02 - Address: 00:14:78:52:51:89 ESSID:"NTC_03" Mode:Master Channel:5 Frequency:2.432 GHz (Channel 5) Quality=43/100 Signal level=-73 dBm Noise level=-71 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s Extra:tsf=00000049daf86181network NTC_03 which is: As far as I know "iwlist" this network uses WEP, right? When I configure connection to this network on second step "Use Wireless Security" is unchecked again. Moreover when I check this option, KNetworkManager suggest me using "WPA Personal" which is not proper as far as I know. Could you explaint to me, what is a reason of this situation? Is there still something to do with KNetworkManager or maybe I am simply doing something wrong?
(In reply to comment #7 from Rafał Miłecki) > Could you explaint to me, what is a reason of this situation? Is there still > something to do with KNetworkManager or maybe I am simply doing something > wrong? True, that's still missing. Comment #5 was only about the WPA not requiring to select the "magic" settings anymore.
Should be fixed in GM (+one online update). Closing as FIXED.