Test environment: HP laptop runs ubuntu-12.04.2 as client side ASUS laptop runs ubuntu-12.04.2 as server side. Set password 12345 in the server side and then use client to connect the server.
If the security type is set to WEP40/128 bit Key, the result is success ( see adhoc/success/syslog.client.log & adhoc/success/syslog.server.log) If the type is set to WEP-128 passphrase, the result is failed (see adhoc/fail/syslog.client.log & adhoc/fail/syslog.server.log) The logs are attached in the tarball. ** Attachment added: "adhoc.tar.gz" https://bugs.launchpad.net/oem-priority/+bug/1032433/+attachment/3753048/+files/adhoc.tar.gz -- 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: New Status in OEM Priority Project precise series: New Status in “network-manager” package in Ubuntu: In Progress 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
