[Bug 194417] [NEW] knetworkmanager misidentifies LEAP network as WEP
charles.figura at wartburg.edu
Fri Feb 22 16:51:46 UTC 2008
Public bug reported:
Binary package hint: knetworkmanager
I'm running knetworkmanager 0.2 under KDE 3.5.8 on kubuntu Gutsy.
Knetworkmanager misidentifies the local LEAP network as WEP.
When I select 'Connect to Other Network' under knetworkmanager and enter
in the correct encryption information, the system can connect to the
LEAP network, and store that network in the 'trusted' network list, as
well as store the encryption information under kwalletmanager (or in the
config file, depending on how that preference is selected).
When I try to reconnect to that network from the list of available
networks, the information misidentifies that network (LEAP) as WEP. The
network information box that pops up when the cursor 'dawdles' over the
network name lists the Encryption Protocal as WEP. Since the stored
login/encryption information is NOT WEP, the connection attempt fails.
When the connection fails, the 'Connect to Wireless Network' box pops up and asks for updated encryption information. Since knetworkmanager thinks the network is WEP, it only offers the WEP encryption options (passphrase, hex, ascii), and does NOT offer the WPA options.
Only when I dismiss this box and select 'Connect to Other Network' can I reconnect to the LEAP network.
This is 100% reproducible.
** Affects: knetworkmanager (Ubuntu)
knetworkmanager misidentifies LEAP network as WEP
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to knetworkmanager in ubuntu.
More information about the kubuntu-bugs