Bug 158248 - knetworkmanager misidentifies LEAP network as WEP
Summary: knetworkmanager misidentifies LEAP network as WEP
Status: RESOLVED DUPLICATE of bug 191120
Alias: None
Product: knetworkmanager
Classification: Unmaintained
Component: 802.1x (show other bugs)
Version: 0.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
: 152627 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-02-23 00:08 UTC by Charlie Figura
Modified: 2009-08-04 09:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Charlie Figura 2008-02-23 00:08:12 UTC
Version:           0.2 (using KDE 3.5.8)
Installed from:    Ubuntu Packages
OS:                Linux

This replaces Bug 152627.
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.
Comment 1 FiNeX 2008-02-24 12:43:41 UTC
*** Bug 152627 has been marked as a duplicate of this bug. ***
Comment 2 Will Stephenson 2009-02-05 17:26:37 UTC
Still a problem with NetworkManager 0.7? 
Comment 3 Charlie Figura 2009-02-05 17:39:46 UTC
No, this bug is no longer valid with v0.7.  HOWEVER, LEAP/PEAP don't work at all for 0.7 now (see Launchpad bug#325462 - https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/325462 )
Comment 4 Will Stephenson 2009-08-04 09:21:33 UTC

*** This bug has been marked as a duplicate of bug 191120 ***