KNetworkManager doesn't use supplied WEP key
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
knetworkmanager |
Invalid
|
Medium
|
|||
knetworkmanager (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Binary package hint: knetworkmanager
On Kubuntu 6.10 with Buffalo WLI-CB-G54A card using Ndiswrapper.
Kubuntu comes up (with a long delay where I suspect it is attempting to connect to the wireless network) and the wireless card's lights are lit but there is no network connection.
I tried this with a test wireless network with no encryption and I connect fine first time - so something to do with WEP.
1) With bare bones /etc/network/
2) If, whilst it is doing this I enter "sudo iwlist wlan0 enc" to check my WEP key, I see a strange key of A7D5-CFE7-
3) SO, while KNetworkManager was trying to connect I entered "sudo iwconfig wlan0 key s:<my wep key>" and I connected fine. This works repeatable for me.
Please let me know what extra info I can supply ... I'd like to be able to connect to the network without having to do the above every time.
Update 4th April:
- strange key is not always the same - today it was 6A80-91FF-
- having entered the correct key through "sudo iwconfig ..." and successfully connected, "sudo iwlist wlan0 enc" shows my correct WEP key
description: | updated |
tags: | added: jaunty |
Changed in knetworkmanager: | |
status: | Unknown → New |
Changed in knetworkmanager: | |
status: | New → Invalid |
Changed in knetworkmanager: | |
importance: | Unknown → Medium |
Syslog from startup included