Confirming the original report - I think. It took me quite some time to figure out how to get WPA working. What I find is that both knetworkmanager (and nm-applet) show my WPA access point as WEP at first, as does "iwlist wlan0 scan". If I select that network both tools will prompt me for a WEP password. However, if I explicitly start wpa_supplicant (which is not initially running) and ask it to do a scan on wlan0, it finds that my access point is WPA, and from that point on both knetworkmanager and nm-applet show the correct encryption type.
My present workaround is to select "Connect to Other Wireless Network" from the knetworkmanager menu, and spell out all the details of the connection explicitly - but that contradicts users' expectations that they should be able to pick a network, type their password, and be connected. It sounds like future versions of NetworkManager use wpa_supplicant directly for scanning, so moving forward on the version might be a good solution. -- WPA2 Personal wireless networks don't work without manual configuration https://bugs.launchpad.net/bugs/106129 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
