[HP Mini 1000 (1030NR)] Cannot connect to WEP encrypted access point BCM4312

[Mark L. Potter]

I am able to connect to any unsecured wireless network with any issues however when I try to connect to a WEP encrytped network I am unable to do so. I have attempted to use nm-applet to connect, verified my settings against a working laptop running Intrepid, and attempted to use the CLI tools to connect and all to no avail.

OS: UNR
Release: 21/04/09 daily release
Driver: Broadcom STA wireless drive (restricted)

Here is the syslog output of an attempted connection:

Apr 21 16:47:11 logen NetworkManager: <info> Activation (eth1) starting connection 'Auto Vanilla'
Apr 21 16:47:11 logen NetworkManager: <info> (eth1): device state change: 3 -> 4
Apr 21 16:47:11 logen NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Apr 21 16:47:11 logen NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Apr 21 16:47:11 logen NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Apr 21 16:47:11 logen NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Apr 21 16:47:11 logen NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Apr 21 16:47:11 logen NetworkManager: <info> (eth1): device state change: 4 -> 5
Apr 21 16:47:11 logen NetworkManager: <info> Activation (eth1/wireless): access point 'Auto Vanilla' has security, but secre
ts are required.
Apr 21 16:47:11 logen NetworkManager: <info> (eth1): device state change: 5 -> 6
Apr 21 16:47:11 logen NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Apr 21 16:47:11 logen NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Apr 21 16:47:11 logen NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Apr 21 16:47:11 logen NetworkManager: <info> (eth1): device state change: 6 -> 4
Apr 21 16:47:11 logen NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Apr 21 16:47:11 logen NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Apr 21 16:47:11 logen NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Apr 21 16:47:11 logen NetworkManager: <info> (eth1): device state change: 4 -> 5
Apr 21 16:47:11 logen NetworkManager: <info> Activation (eth1/wireless): connection 'Auto Vanilla' has security, and secrets
 exist. No new secrets needed.
Apr 21 16:47:11 logen NetworkManager: <info> Config: added 'ssid' value 'Vanilla'
Apr 21 16:47:11 logen NetworkManager: <info> Config: added 'scan_ssid' value '1'
Apr 21 16:47:11 logen NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
Apr 21 16:47:11 logen NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
Apr 21 16:47:11 logen NetworkManager: <info> Config: added 'wep_key0' value '<omitted>'
Apr 21 16:47:11 logen NetworkManager: <info> Config: added 'wep_key1' value '<omitted>'
Apr 21 16:47:11 logen NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0'
Apr 21 16:47:11 logen NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' fa
iled
Apr 21 16:47:11 logen NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' fa
iled
Apr 21 16:47:11 logen NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Apr 21 16:47:11 logen NetworkManager: <info> Config: set interface ap_scan to 1
Apr 21 16:47:11 logen NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
Apr 21 16:47:11 logen NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
Apr 21 16:47:16 logen NetworkManager: <info> (eth1): supplicant connection state: scanning -> associating
Apr 21 16:47:17 logen NetworkManager: <info> (eth1): supplicant connection state: associating -> associated
Apr 21 16:47:17 logen NetworkManager: <info> (eth1): supplicant connection state: associated -> completed
Apr 21 16:47:17 logen NetworkManager: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful. Connect
ed to wireless network 'Vanilla'.
Apr 21 16:47:17 logen NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 21 16:47:17 logen NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
Apr 21 16:47:17 logen NetworkManager: <info> (eth1): device state change: 5 -> 7
Apr 21 16:47:17 logen NetworkManager: <info> Activation (eth1) Beginning DHCP transaction.
Apr 21 16:47:17 logen NetworkManager: <info> dhclient started with pid 7204
Apr 21 16:47:17 logen NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Apr 21 16:47:17 logen dhclient: Internet Systems Consortium DHCP Client V3.1.1
Apr 21 16:47:17 logen dhclient: Copyright 2004-2008 Internet Systems Consortium.
Apr 21 16:47:17 logen dhclient: All rights reserved.
Apr 21 16:47:17 logen dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Apr 21 16:47:17 logen dhclient:
Apr 21 16:47:17 logen NetworkManager: <info> DHCP: device eth1 state changed normal exit -> preinit
Apr 21 16:47:17 logen dhclient: Listening on LPF/eth1/00:24:2b:99:af:a8
Apr 21 16:47:17 logen dhclient: Sending on LPF/eth1/00:24:2b:99:af:a8
Apr 21 16:47:17 logen dhclient: Sending on Socket/fallback
Apr 21 16:47:17 logen dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
Apr 21 16:47:26 logen dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
Apr 21 16:47:41 logen dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 21
Apr 21 16:48:02 logen dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
Apr 21 16:48:03 logen NetworkManager: <info> Device 'eth1' DHCP transaction took too long (>45s), stopping it.
Apr 21 16:48:03 logen NetworkManager: <info> eth1: canceled DHCP transaction, dhcp client pid 7204
Apr 21 16:48:03 logen NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Timeout) scheduled...
Apr 21 16:48:03 logen NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Timeout) started...
Apr 21 16:48:03 logen NetworkManager: <info> Activation (eth1/wireless): could not get IP configuration for connection 'Auto Vanilla'.
Apr 21 16:48:03 logen NetworkManager: <info> (eth1): device state change: 7 -> 6
Apr 21 16:48:03 logen NetworkManager: <info> Activation (eth1/wireless): asking for new secrets
Apr 21 16:48:03 logen NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Timeout) complete.
Apr 21 16:48:11 logen NetworkManager: <WARN> get_secrets_cb(): Couldn't get connection secrets: applet-device-wifi.c.1539 (get_secrets_dialog_response_cb): canceled.

I will gladly provide any other log files or information needed.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
IfupdownConfig:
 auto lo
 iface lo inet loopback
Package: network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
Tags: ubuntu-unr
Uname: Linux 2.6.28-11-generic i686

[Tony Espy (awe)]

A couple of questions...

1. Have you tried to connect to any other WEP access points besides "Vanilla"? Any success?

2. Do you have any admin rights for "Vanilla"? It'd be interesting to try and test whether you can connect to "Vanilla" if it's security was disabled and/or changed to "WPA-Personal"?

The problem seems to be that you cannot get an IP address from the AP. Usually when this happens, it's due to an incorrect key being entered. When you enter a key in the Auth Required Dialog, what does the "Wireless security" combo display?

[Maarten Bezemer (veger)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 364869 and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]