At this point it's still unclear whether we're really seeing the same
problem as earlier.
In the latest logs, I see the client creates its own BSSID -- this means
it doesn't see the AP on the other end, which probably also means one or
both of the devices can't do AdHoc properly even if it claims it can.
In the earlier logs (adhoc.tar.gz), I see the client and server get
successfully connected to the same BSSID, but traffic does not flow.
This could indeed be due to an issue in recognizing the passphrases
being the same keys.
I also see significant differences in the hostnames for the devices
between the two sets of tests, which means it's likely different
machines -- so different hardware between both tests, which would easily
explain the different behavior.
All this to say that it doesn't seem to me like what's happening here
between the two cases is the same bug at all, even if it looks similar.
In addition, since we're dealing with ad-hoc and specifically WEP-128
passphrase, which is just a wrapper to use standard WEP keys, please
make sure adhoc works properly with the standard WEP keys in all the
tested cases here.
I can't see any indication that there has been a fix for such a bug in
NM -- so there's for now no patch I can apply to fix this immediately.
This will definitely need more testing.
Could you please run wpasupplicant in debug mode (add -ddd to the Exec=
line in /usr/share/dbus-1/system-
services/fi.w1.wpa_supplicant1.service), and provide more logs with the
same tests?
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
--
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:
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
