Can't connect to WEP-encrypted networks using "Shared Key" because "Open System" is always used instead

Bug #162413 reported by iGadget
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

When connecting to a WEP-encrypted WiFi network, using 'Shared Key' as authentication method, the system uses the 'Open System' authentication method instead. At least, this is my suspicion when I try to connect to such a network and I'm not getting access (while the credentials are okay). Opening a console and typing 'dmesg' produces the following output:

[ 1997.197199] SoftMAC: Open Authentication with 00:0e:a6:63:10:b5 failed, error code: 1
[ 1997.558916] SoftMAC: Open Authentication with 00:0e:a6:63:10:b5 failed, error code: 1

This message is repeated several times.

When I'm using WinXP on the same machine, connecting to the same network, using the same credentials, the connection is established without any problems.

System info:

HP Pavilion zv6000 (broadcom bcm43xx)
Ubuntu 7.10

Revision history for this message
apetrelli (antonio-petrelli) wrote :

Is this bug connected to KNetworkManager?
I previously used wlassistant to connect.
Under Feisty, wlassistant 0.5.5 works well, while under gutsy, wlassistant 0.5.7 does not work.
It seems that 0.5.5 used the command:
iwconfig wlan0 essid MYESSID key s:MYKEY
while under 0.5.7 it does not use it correctly: it uses a different technique that I cannot remember.
I think it is a wrong use of iwconfig bug of KNetworkManager, not a driver problem.

I tested:
TRENDnet TEW 424UB (USB) with Realtek Chipset
Intel Wireless (can't remember the model).

Revision history for this message
iGadget (igadget) wrote :

I really don't know if this bug is connected to KNetworkManager, since I don't use KDE. Can anyone else confirm this (and my problem)? :)

Revision history for this message
iGadget (igadget) wrote : Slightly different error when using a 'freshly' booted machine

I'm also getting this slightly different error when following the steps mentioned above, but with a 'freshly' booted machine:

SoftMAC: Open Authentication with 00:0e:a6:63:10:b5 failed, error code: 13

I don't know if this makes any difference, but the problem is just as annoying (having to type this in Windows because I can't connect using Ubuntu).

Revision history for this message
Leann Ogasawara (leannogasawara) wrote : Re: Connecting to WEP-encrypted networks using shared key impossible

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add your '/var/log/syslog' file as an attachment to your bug report? Thanks in advance.

Changed in network-manager:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in network-manager:
status: Incomplete → Invalid
Revision history for this message
apetrelli (antonio-petrelli) wrote :

What do you need more?
If you use a WEP-encrypted network with shared key authentication, it's impossible to connect.
At least, it does not work with KNetworkManager under Kubuntu.

Revision history for this message
Alberto Donato (ack) wrote :

I have this problem on Karmic beta, when trying to connect to a WEP network with shared key, NM keeps asking the key.
Editing connections, I see "Open System" is selected by default, manually changing it to "Shared Key" solves the problem.

This is wpa-supplicant log with the default settings:

Oct 25 12:32:25 endor NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto MyNetwork' has security, and secrets exist. No new secrets needed.
Oct 25 12:32:25 endor NetworkManager: <info> Config: added 'ssid' value 'MyNetwork'
Oct 25 12:32:25 endor NetworkManager: <info> Config: added 'scan_ssid' value '1'
Oct 25 12:32:25 endor NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
Oct 25 12:32:25 endor NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
Oct 25 12:32:25 endor NetworkManager: <info> Config: added 'wep_key0' value '<omitted>'
Oct 25 12:32:25 endor NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0'

and after configuration change:

Oct 25 12:32:49 endor NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto MyNetwork' has security, and secrets exist. No new secrets needed.
Oct 25 12:32:49 endor NetworkManager: <info> Config: added 'ssid' value 'MyNetwork'
Oct 25 12:32:49 endor NetworkManager: <info> Config: added 'scan_ssid' value '1'
Oct 25 12:32:49 endor NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
Oct 25 12:32:49 endor NetworkManager: <info> Config: added 'auth_alg' value 'SHARED'
Oct 25 12:32:49 endor NetworkManager: <info> Config: added 'wep_key0' value '<omitted>'
Oct 25 12:32:49 endor NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0'

Changed in network-manager (Ubuntu):
status: Invalid → New
Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't start working on it yet, because your bug report didn't include enough information.

Using Karmic 9.10, please include the information requested at https://wiki.ubuntu.com/DebuggingNetworkManager. If you have trouble, please do not hesitate to ask for more assistance. Thanks in advance.

Changed in network-manager (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Alberto Donato (ack)
tags: added: encryption-wep
Revision history for this message
Alberto Donato (ack) wrote :

Here is the full syslog, intermixed with the action performed. The network is a WPA protected network, with shared key.
When selecting the wireless network the first time, the key is asked but Authentication is set to "Open System" by default (while "Shared key" is the right setting).

Revision history for this message
kai (kaihelen-deactivatedaccount) wrote :

I ve been trying for hours and hours to access wireless no trouble ethernet wired or vodaphone mobile but it will not connect to livebox tried taking of live box security tried loads of commands and still no luck seems a serious bug to me and a fatal one to ubuntu for anyone with laptop or netbook as you can only use it with wired connection
kai

Revision history for this message
kai (kaihelen-deactivatedaccount) wrote :

I am at present trying to follow question #93070 where all info stored for your information
kai

Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

Thank you for the update and supplying the information. This has now been marked Triaged, which means there should be enough information for a developer to begin debugging this, so I am leaving it in their capable hands. Thanks again for reporting this to us, and good luck! :)

Changed in network-manager (Ubuntu):
status: Incomplete → Triaged
tags: added: karmic
Revision history for this message
Thomas Hood (jdthood) wrote :

Is this still a bug in Precise?

summary: - Connecting to WEP-encrypted networks using shared key impossible
+ Can't connect to WEP-encrypted networks using "Shared Key" because "Open
+ System" is always used instead
Revision history for this message
iGadget (igadget) wrote :

Sorry, I don't have access to that specific network anymore (for several years now). But I guess it would be easy enough for anyone with some spare time (which I currently lack completely) and a WiFi accesspoint to configure it to use WEP and try to connect?

Thomas Hood (jdthood)
Changed in network-manager (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.