Looks like in both cases wpa-supplicant got past the authentication stage. Oddly, even though it should not work in the second trial, it still gets past authentication.
The problem with the first trial is that it couldn't get a dhcp lease, which makes me think it's a problem on the other machine. Would you please attach a syslog from that machine as well? -- 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: Incomplete Status in OEM Priority Project precise series: Incomplete Status in “network-manager” package in Ubuntu: Incomplete 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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
