Is this bug connected to KNetworkManager? I previously used wlassistant to connect. Under Feisty, wlassistant 0.5.5 works well, while under gutsy, wlassistant 0.5.7 does not work. It seems that 0.5.5 used the command: iwconfig wlan0 essid MYESSID key s:MYKEY while under 0.5.7 it does not use it correctly: it uses a different technique that I cannot remember. I think it is a wrong use of iwconfig bug of KNetworkManager, not a driver problem.
I tested: TRENDnet TEW 424UB (USB) with Realtek Chipset Intel Wireless (can't remember the model). -- Connecting to WEP-encrypted networks using shared key impossible https://bugs.launchpad.net/bugs/162413 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
