** Changed in: oem-priority
Status: Confirmed => Won't Fix
** No longer affects: oem-priority/precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032433
Title:
Using WEP 128-bit
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
Attach syslog for client and server side.
The wpa_supplication debug output (-ddd option) is enabled.
** Attachment added: syslog.wpa.tgz
https://bugs.launchpad.net/oem-priority/+bug/1032433/+attachment/4029646/+files/syslog.wpa.tgz
--
You received this bug notification because you are a
syslog of comment #21
** Attachment added: syslog.wpa.client.trusty
https://bugs.launchpad.net/oem-priority/+bug/1032433/+attachment/4030075/+files/syslog.wpa.client.trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The same issue can be reproduced on Trusty (14.04)
The attachment is the syslog on same platform but is installed with
trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032433
Title:
Using
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: oem-priority
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032433
** Changed in: oem-priority
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032433
Title:
Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
To
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
Attach logs.
Config WiFi adhoc network and set WEP key to 1234567890abc.
The connection can't be established.
Logs are attached (server/client side dmesg output and syslog)
** Attachment added: wifi_adhoc_log.tgz
** Changed in: network-manager (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) = Mathieu
Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032433
Can we get someone to have a look to this bug, please?
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Canonical Desktop Team (canonical-desktop-team)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: oem-priority/precise
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032433
@James,
Update log files.
I use '1234567890abc' as wep key, here are the fail logs of client/server both
sides.
Note, I aslo tested the key in hex format ( 31323334353637383930616263 ), it
failed too. The logs are attached.
--
You received this bug notification because you are a member of
Franz,
12345 from the server side looks like a 40 bit key (8 bits per
character, multiplied by 5 characters). This would explain why it's
working when you use that option. In order to be completely sure that
it's not a 40 bit key, would you please re-create your server
environment with a WEP-128
** Changed in: network-manager (Ubuntu)
Status: In Progress = Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Low = Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
Reopening the OEM priority bug, as there are some OEMs still requesting
this
** Changed in: oem-priority
Status: Won't Fix = New
** Changed in: oem-priority
Assignee: James M. Leddy (jm-leddy) = Ara Pulido (apulido)
** Changed in: oem-priority/precise
Status: Won't Fix = New
Because this does not block certification of systems, we are closing the
bug in OEM prio for now.
** Changed in: oem-priority/precise
Status: In Progress = Won't Fix
** Changed in: oem-priority
Status: In Progress = Won't Fix
** Changed in: network-manager (Ubuntu)
Importance:
Are both machines running Ubuntu, and are they using the same version?
Can you provide the debug logs for wpasupplicant? This would likely shed
more light on the problem.
Furthermore, I'd be very interested on output such as what the Android
Wifi Analyzer app is saying about the created network,
** Changed in: oem-priority
Status: Incomplete = In Progress
** Changed in: oem-priority/precise
Status: Incomplete = In Progress
** Changed in: network-manager (Ubuntu)
Status: Incomplete = In Progress
--
You received this bug notification because you are a member of
I was able to reproduce this using my dev laptop and a netbook, both
running Precise.
I created the adhoc network on my laptop, then tried and failed to
connect using the NetworkManager applet on the netbook.
I then dropped to the command line on the netbook and manually connected
using
** Changed in: oem-priority
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032433
Title:
Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
To
** Changed in: oem-priority/precise
Status: Confirmed = Invalid
** Changed in: oem-priority/precise
Status: Invalid = Incomplete
** Changed in: oem-priority
Status: Confirmed = Invalid
** Changed in: oem-priority
Status: Invalid = Incomplete
--
You received this
** Changed in: oem-priority
Status: Incomplete = Confirmed
** Changed in: oem-priority/precise
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032433
** Tags removed: rls-q-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032433
Title:
Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
To manage notifications about
Affects me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032433
Title:
Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
To manage notifications about this bug go to:
@James: please readd rls-q-incoming if you get more directions on the
user's machine, and we'll deal with it. Thanks :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032433
Title:
Using WEP
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.
Hi,
I can still reproduce this on 12.04.1
First I setup an Ad-hoc connection with WEP 128-bit Passphrase on Computer1,
and using another computer (ComputerU) as client to connect, but the connection
cannot be established, attached file is syslog on ComputerU (client).
** Attachment added:
And then I create new ad-hoc connection test2 on computer1 using WEP
40/128-bit Key(Hex or ASCII), this time I can use ComputerU (client) to
establish an ad-hoc connection successfully.
Attached file is the syslog of this connection.
** Attachment added: syslog_success
@James,
I have asked Nara help to provide more information in comment#4 and
comment#5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032433
Title:
Using WEP 128-bit Passphrase, Ad-hoc connection
Hi Mathieu,
I just tried to reproduce the issue, but was unable to. I'll get more
information from Kent.
** Changed in: oem-priority
Status: Confirmed = Incomplete
** Changed in: oem-priority/precise
Status: Confirmed = Incomplete
--
You received this bug notification because
Does anyone even use WEP passpharase mode? Can we just remove this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032433
Title:
Using WEP 128-bit Passphrase, Ad-hoc connection cannot be
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
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032433
Title:
Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
To manage notifications about this
** Changed in: oem-priority
Status: New = Confirmed
** Changed in: oem-priority/precise
Status: New = Confirmed
** Changed in: oem-priority
Assignee: (unassigned) = James M. Leddy (jm-leddy)
** Changed in: oem-priority/precise
Assignee: (unassigned) = James M. Leddy
** Also affects: oem-priority
Importance: Undecided
Status: New
** Also affects: oem-priority/precise
Importance: Undecided
Status: New
** Changed in: oem-priority/precise
Importance: Undecided = High
--
You received this bug notification because you are a member of
37 matches
Mail list logo
