NM doesn't really ask for the type of key when you get to connecting to the previously-created network. It's however possible to create the connection, and then edit it from the connection editor to set "WEP passphrase" and enter in the passphrase, which will allow the connection to work.
Not sure we'll be able to land a fix for this just now, given how late in the cycle it is. I can however start figuring out how to add the feature properly and submit it for review from the upstream developers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1032433 Title: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established Status in OEM Priority Project: Confirmed Status in OEM Priority Project precise series: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Bug description: When setting up an ad-hoc wifi connection, if choose "WEP 128-bit Passphrase", the connection cannot be established. If choose "None" or "WEP 40/128-bit Key", it can be established successfully. Steps to reproduce: 1. Choose "Create new Wireless Network" in network applet 2. Choose "WEP 128-bit Passphrase" and create an ad-hoc connection 3. Use another computer to connect the same ad-hoc ESSID 4. The connection cannot be established To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1032433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
