No, WEP passphrase does get used... it's much easier to use a passphrase
than the hex keys, at least ;)
This bug needs additional information in order to be debuggable. Could
you please run 'apport-collect 1032433' and make sure at least
WifiSyslog.txt is attached automatically. If not, please include at
least an excerpt of /var/log/syslog for an attempted connection.
Thanks in advance!
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
--
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:
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 : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
