WEP is listed on WPA configure AP.

Bug #59549 reported by Denis Moyogo Jacquerye
8
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

I' m trying to connect to a WPA secured wireless network with network manager.

Network manager only displays WEP choices for Wireless Security.
Can' t it use WPA with username, password and domain?

Revision history for this message
Denis Moyogo Jacquerye (moyogo) wrote :

hmmm this is weird.
if I just try to connect to an already listed network, only WEP* are listed as Wireless Security. But if I try to connect by clicking on the "Connect to Other Wireless Network" then Wireless Security lists WPA and WPA2.

Revision history for this message
Riccardo Setti (giskard) wrote :

did your driver support WPA ?

afaik NM uses wpa_supplicant for do this kind of stuff.

 Can you connect to the WPA network wit wpa_supplicant?

Revision history for this message
Denis Moyogo Jacquerye (moyogo) wrote :

I haven't tried connecting with wpa_supplicant, but the driver (ipw) does have WPA support.

Revision history for this message
Scott Robinson (scott-ubuntu) wrote :

Have you tried connecting with WPA with the "Connect to Other Wireless Network" method?

NM detects the encryption announced by the router, so if it isn't showing the WPA option there is an issue with the AP.

If you can connect with the above method, let me know so we can get your debugging output and report a bug upstream.

Revision history for this message
GiuseppeVerde (launchpad-digitasaru) wrote :

I am seeing similar behavior, which is particularly aggravating under poor signal conditions. Windows and Mac notebooks seem to not have a problem, and it's extremely frustrating having to manually enter the whole information over and over and over again.

The problems are:
  1) the UIowa WPA network uses dynamic WEP, and it is detected as static WEP. Somehow, this works for Windows and Mac, but not for N-M.
  2) links seem to be randomly dropped.
  3) N-M forgets about the network and I have to keep manually entering in the informaiton (very annoying after the 15th dissassociation)!

Attached is a log of frustration (grep -i networkmanager /var/log/syslog).

This is independent of networking device because it happens for both my ipw2100 as well as madwifi card.

Revision history for this message
Bernie Bernstein (bernie9998) wrote :

I had experienced the same issue with both Feisty Fawn and Sabayon Linux on my thinkpad t30.

It has an intersil prism2.5 pci card, using the hostap driver.

It appears that NetworkManager misinterprets or otherwise fails to scan for networks properly. However, I did discover a workaround:

1: stop NetworkManager
2: start wpa_supplicant with control interface
3: initiate a scan with wpa_cli
4: kill wpa_supplicant
5: start NetworkManager

After doing this, I find that the list of networks now show WPA flags on the details that pop up, and when selecting one, it now prompts for the appropriate wpa password instead of having wep as the only option.

I am not sure if this fixes NetworkManager with successive scans, I get the sense that it will not. Until a real fix is created, I'm simply adding the steps above in the NetworkManager init scripts for now.

Revision history for this message
John Vivirito (gnomefreak) wrote :

What version of ubuntu, network-manager, and wpasupplicant ar eyou using? If this is gutsy can you please attach the output of lspci -v and the file: /var/log/syslog to this bug report.

Changed in network-manager:
status: New → Incomplete
Revision history for this message
Alexander Sack (asac) wrote :

I know this bug ... but for me it has disappeared during gutsy development cycle. If you still see it, please reopen this bug.

Changed in network-manager:
status: Incomplete → Fix Released
Revision history for this message
Brad Taylor (brad) wrote :

I'm seeing this bug on my Thinkpad X30 (Prism 2.5), but I'm not seeing it with my Thinkpad T61 (Intel 3945ABG). Both are running the latest Gutsy.

Both have:
network-manager 0.6.5-0ubuntu16.7.10.0
wpasupplicant 0.6.0+0.5.8-0ubuntu1

Attaching syslog and lspci -v

Revision history for this message
Brad Taylor (brad) wrote :
Changed in network-manager:
status: Fix Released → Confirmed
Revision history for this message
Joan Maria Talarn (jmtalarn) wrote :

Hello to everybody,

I get the same error!
But I have a contribution:
When I boot with the LiveCD networkManager detected the network and his encryption! After the installation It didn't detect anymore the WPA encryption in the network and manual configuration didn't work too!

I reported this to the Ubuntuforums too : http://ubuntuforums.org/showthread.php?t=695531

Revision history for this message
Joan Maria Talarn (jmtalarn) wrote :

Hi!

I found a solution to my problem!!!

Finally I copied all /lib/modules/2.6.22-14-generic/ from LiveCd to the installed one.

And after this, Ubuntu booted taking a little more time but Now it detects the network and his security, it prompts me for the WPA personal, I introduce it and it connect!

What will be the difference between the LiveCD and the installation?

Well! Was Hard!

Revision history for this message
aduplat (alduplat) wrote :

Hi:

I tried to find this: /lib/modules/2.6.22-14-generic/ on my live CD but I couldn't.

Could somebody tell me where I can find this ... and where I have to copy.

Thanks,

Revision history for this message
Alexander Sack (asac) wrote :

I havent seen this for a long time so i assume that this is at least fixed in NM 0.7 (intrepid) ... if not in 0.6.6 (hardy).
Please reopen if i am mistaken and missed the point ;).

Thanks!

Changed in network-manager:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.