Activity log for bug #102502

Date Who What changed Old value New value Message
2007-04-03 18:42:20 Nick Bridgwater bug added bug
2007-04-04 08:35:25 Nick Bridgwater 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/interfaces file, I attempt to connect to my wireless n/w using KNetworkManager with the correct WEP key specified. It fails to connect and reprompts for my WEP key ... 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-B0B7-EB11-E518-17FE-B4 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. 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/interfaces file, I attempt to connect to my wireless n/w using KNetworkManager with the correct WEP key specified. It fails to connect and reprompts for my WEP key ... 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-B0B7-EB11-E518-17FE-B4 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-2462-08C2-2639-7459-52 - having entered the correct key through "sudo iwconfig ..." and successfully connected, "sudo iwlist wlan0 enc" shows my correct WEP key
2007-04-04 16:38:20 Nick Bridgwater bug added attachment 'Syslog trace startup' (Syslog from startup)
2007-04-05 09:54:41 Nick Bridgwater bug added attachment 'Syslog Boot' (Syslog from boot above)
2007-04-05 09:56:32 Nick Bridgwater bug added attachment 'Syslog KNM connect failure' (Syslog from failure to connect with KNM)
2007-04-05 09:59:42 Nick Bridgwater bug added attachment 'Syslog KNM connect success' (Syslog KNM connect success)
2007-07-21 08:18:39 Sujee Maniyam knetworkmanager: status New Incomplete
2007-07-21 08:18:39 Sujee Maniyam knetworkmanager: statusexplanation
2009-04-07 09:22:00 Achim Spangler tags wep jaunty wep
2009-04-07 09:41:34 Achim Spangler attachment added relevant part of /var/log/syslog http://launchpadlibrarian.net/24927359/log.txt
2009-04-07 09:43:05 Achim Spangler knetworkmanager (Ubuntu): status Invalid New
2009-05-18 16:30:32 xteejx knetworkmanager (Ubuntu): status New Incomplete
2009-05-19 16:33:27 xteejx bug watch added http://bugs.kde.org/show_bug.cgi?id=193257
2009-05-19 16:33:27 xteejx bug task added knetworkmanager
2009-05-19 16:36:46 xteejx knetworkmanager (Ubuntu): importance Undecided Medium
2009-05-19 16:36:46 xteejx knetworkmanager (Ubuntu): status Incomplete Triaged
2009-05-19 17:10:35 Bug Watch Updater knetworkmanager: status Unknown New
2009-09-03 15:27:57 Jonathan Thomas knetworkmanager (Ubuntu): status Triaged Won't Fix
2010-01-11 23:49:18 xteejx removed subscriber Teej
2010-01-27 14:41:34 Bug Watch Updater knetworkmanager: status New Invalid
2011-02-03 12:52:35 Bug Watch Updater knetworkmanager: importance Unknown Medium