Ubuntu
network-manager package

[madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to wireless network

Bug #199802 reported by Chris MacDonald
24
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Committed
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

Since upgrading to alpha 6 earlier today and rebooting I haven't been able to connect to my WPA1 network at home using NetworkManager. I've removed all preexisting wireless settings for the application and started fresh, selected the network from the list shown, made sure the correct type of network was chosen and the correct encryption, entered the key and NetworkManager proceeds to churn away for two minutes then give up.

This is a connection attempt:

root@pea:/var/run# /usr/sbin/NetworkManager --pid-file /var/run/NetworkManager/NetworkManager.pid --no-daemon
NetworkManager: <info> starting...
NetworkManager: <info> ath0: Device is fully-supported using driver 'ath_pci'.
NetworkManager: <info> ath0: driver does not support SSID scans (scan_capa 0x00).
NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
NetworkManager: <info> Now managing wireless (802.11) device 'ath0'.
NetworkManager: <info> Deactivating device ath0.
NetworkManager: <info> eth0: Device is fully-supported using driver 'tg3'.
NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
NetworkManager: <info> Deactivating device eth0.
NetworkManager: <info> Updating allowed wireless network lists.
NetworkManager: <WARN> nm_dbus_get_networks_cb(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored..
NetworkManager: <debug> [1204975359.657036] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'ALBATROSS'
NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/ath0 / ALBATROSS
NetworkManager: <info> Deactivating device ath0.
NetworkManager: <info> Device ath0 activation scheduled...
NetworkManager: <info> Activation (ath0) started...
NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <info> Activation (ath0/wireless): access point 'ALBATROSS' is encrypted, but NO valid key exists. New key needed.
NetworkManager: <info> Activation (ath0) New wireless user key requested for network 'ALBATROSS'.
NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete.
NetworkManager: <info> Activation (ath0) New wireless user key for network 'ALBATROSS' received.
NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <info> Activation (ath0/wireless): access point 'ALBATROSS' is encrypted, and a key exists. No new key needed.
NetworkManager: <info> SUP: sending command 'INTERFACE_ADD ath0 wext /var/run/wpa_supplicant0 '
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
NetworkManager: <info> SUP: response was '0'
NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 414c424154524f5353'
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 proto WPA'
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 psk <key>'
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete.
Trying to associate with 00:0f:66:38:cc:cd (SSID='ALBATROSS' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:0f:66:38:cc:cd (SSID='ALBATROSS' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:0f:66:38:cc:cd (SSID='ALBATROSS' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:0f:66:38:cc:cd (SSID='ALBATROSS' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:0f:66:38:cc:cd (SSID='ALBATROSS' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:0f:66:38:cc:cd (SSID='ALBATROSS' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:0f:66:38:cc:cd (SSID='ALBATROSS' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:0f:66:38:cc:cd (SSID='ALBATROSS' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:0f:66:38:cc:cd (SSID='ALBATROSS' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
NetworkManager: <info> Activation (ath0/wireless): association took too long (>120s), failing activation.
NetworkManager: <info> Activation (ath0) failure scheduled...
Trying to associate with 00:0f:66:38:cc:cd (SSID='ALBATROSS' freq=2437 MHz)
NetworkManager: <info> Activation (ath0) failed for access point (ALBATROSS)
NetworkManager: <info> Activation (ath0) failed.
NetworkManager: <info> Deactivating device ath0.
CTRL-EVENT-TERMINATING - signal 15 received
sendmsg(CTRL_IFACE monitor): No such file or directory

Conversely I'm able to connect manually using wpa_supplicant and dhclient:

root@pea:~# /sbin/wpa_supplicant -Dmadwifi -iath0 -c /etc/wpa_supplicant/wpa_supplicant.conf
Trying to associate with 00:0f:66:38:cc:cd (SSID='ALBATROSS' freq=2437 MHz)
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
Association request to the driver failed
Associated with 00:0f:66:38:cc:cd
WPA: Key negotiation completed with 00:0f:66:38:cc:cd [PTK=CCMP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:0f:66:38:cc:cd completed (auth) [id=0 id_str=]
---------------
root@pea:/var/run# dhclient ath0
There is already a pid file /var/run/dhclient.pid with pid 8570
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:11:f5:61:7a:12
Sending on LPF/ath0/00:11:f5:61:7a:12
Sending on Socket/fallback
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 10.0.0.1
bound to 10.0.0.17 -- renewal in 95076 seconds.

My wpa_supplicant.conf looks like this:

ctrl_interface=/var/run/wpa_supplicant-global
update_config=1

network={
  ssid="ALBATROSS"
  proto=WPA
  key_mgmt=WPA-PSK
  pairwise=CCMP TKIP
  group=CCMP TKIP
  psk="key"
}

Prior to upgrading the connection worked as expected; it would store settings and reconnect automatically. I haven't had the opportunity to try open networks to see if I get similar results as others depend on this particular network being up so I'll take my laptop to a coffee shop tomorrow and try it out.

Other generic, possibly helpful information...

cmacdonald@pea:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"
cmacdonald@pea:~$ apt-cache policy network-manager
network-manager:
  Installed: 0.6.6-0ubuntu1
  Candidate: 0.6.6-0ubuntu1
  Version table:
 *** 0.6.6-0ubuntu1 0
        500 http://us.archive.ubuntu.com hardy/main Packages
        500 http://archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

cmacdonald@pea:~$ uname -a
Linux pea 2.6.24-11-generic #1 SMP Fri Feb 29 22:08:31 UTC 2008 i686 GNU/Linux
cmacdonald@pea:~$ modinfo ath_pci
filename: /lib/modules/2.6.24-11-generic/madwifi/ath_pci.ko
license: Dual BSD/GPL
version: 0.9.3.3
description: Support for Atheros 802.11 wireless LAN cards.
author: Errno Consulting, Sam Leffler
srcversion: 64AD740F085A20BCC0C8478
alias: pci:v0000168Cd00009013sv*sd*bc*sc*i*
alias: pci:v0000168Cd0000001Dsv*sd*bc*sc*i*
alias: pci:v0000168Cd0000001Csv*sd*bc*sc*i*
alias: pci:v0000168Cd0000001Bsv*sd*bc*sc*i*
alias: pci:v0000168Cd0000001Asv*sd*bc*sc*i*
alias: pci:v0000168Cd00000019sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000018sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000017sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000016sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000015sv*sd*bc*sc*i*
alias: pci:v0000168Cd0000101Asv*sd*bc*sc*i*
alias: pci:v0000168Cd00001014sv*sd*bc*sc*i*
alias: pci:v000010B7d00000013sv*sd*bc*sc*i*
alias: pci:v0000A727d00000013sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000013sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000012sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000007sv*sd*bc*sc*i*
depends: ath_hal,wlan
vermagic: 2.6.24-11-generic SMP mod_unload 586
parm: countrycode:Override default country code (int)
parm: outdoor:Enable/disable outdoor use (int)
parm: xchanmode:Enable/disable extended channel mode (int)
parm: rfkill:Enable/disable RFKILL capability (int)
parm: autocreate:Create ath device in [sta|ap|wds|adhoc|ahdemo|monitor] mode. defaults to sta, use 'none' to disable (charp)
parm: ratectl:Rate control algorithm [amrr|onoe|sample], defaults to 'sample' (charp)
parm: ath_debug:Load-time debug output enable (int)

Please let me know if I can contribute other logs, test anything or help out in any other way. Thanks.

*** UPDATE ***

Grabbed a coffee this afternoon and wasn't able to connected to an open network using NetworkManager either, though a manual connection using wpa_supplicant worked fine.

NetworkManager output:

root@pea:~# /usr/sbin/NetworkManager --pid-file /var/run/NetworkManager/NetworkManager.pid --no-daemon
NetworkManager: <info> starting...
NetworkManager: <info> ath0: Device is fully-supported using driver 'ath_pci'.
NetworkManager: <info> ath0: driver does not support SSID scans (scan_capa 0x00).
NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
NetworkManager: <info> Now managing wireless (802.11) device 'ath0'.
NetworkManager: <info> Deactivating device ath0.
NetworkManager: <info> eth0: Device is fully-supported using driver 'tg3'.
NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
NetworkManager: <info> Deactivating device eth0.
NetworkManager: <info> Updating allowed wireless network lists.
NetworkManager: <WARN> nm_dbus_get_networks_cb(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored..
NetworkManager: <debug> [1205015702.267368] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'WAVES Wireless - Framework N01'
NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/ath0 / WAVES Wireless - Framework N01
NetworkManager: <info> Deactivating device ath0.
NetworkManager: <info> Device ath0 activation scheduled...
NetworkManager: <info> Activation (ath0) started...
NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <info> Activation (ath0/wireless): access point 'WAVES Wireless - Framework N01' is unencrypted, no key needed.
NetworkManager: <info> SUP: sending command 'INTERFACE_ADD ath0 wext /var/run/wpa_supplicant0 '
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
NetworkManager: <info> SUP: response was '0'
NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 574156455320576972656c657373202d204672616d65776f726b204e3031'
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete.
Trying to associate with 00:13:10:f1:59:9e (SSID='WAVES Wireless - Framework N01' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:13:10:f1:59:9e (SSID='WAVES Wireless - Framework N01' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:13:10:f1:59:9e (SSID='WAVES Wireless - Framework N01' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:13:10:f1:59:9e (SSID='WAVES Wireless - Framework N01' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:13:10:f1:59:9e (SSID='WAVES Wireless - Framework N01' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:13:10:f1:59:9e (SSID='WAVES Wireless - Framework N01' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:13:10:f1:59:9e (SSID='WAVES Wireless - Framework N01' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:13:10:f1:59:9e (SSID='WAVES Wireless - Framework N01' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
Trying to associate with 00:13:10:f1:59:9e (SSID='WAVES Wireless - Framework N01' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NetworkManager: <info> Old device 'ath0' activating, won't change.
NetworkManager: <info> Activation (ath0/wireless): association took too long (>120s), failing activation.
NetworkManager: <info> Activation (ath0) failure scheduled...
Trying to associate with 00:13:10:f1:59:9e (SSID='WAVES Wireless - Framework N01' freq=2437 MHz)
NetworkManager: <info> Activation (ath0) failed for access point (WAVES Wireless - Framework N01)
NetworkManager: <info> Activation (ath0) failed.
NetworkManager: <info> Deactivating device ath0.
CTRL-EVENT-TERMINATING - signal 15 received
sendmsg(CTRL_IFACE monitor): No such file or directory

Output from connecting with wpa_supplicant:

root@pea:~# wpa_supplicant -Dmadwifi -iath0 -c/etc/wpa_supplicant/wpa_supplicant.conf
Trying to associate with 00:1c:10:0a:1f:bd (SSID='WAVES Wireless - Framework N02' freq=2412 MHz)
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
Association request to the driver failed
Associated with 00:1c:10:0a:1f:bd
CTRL-EVENT-CONNECTED - Connection to 00:1c:10:0a:1f:bd completed (auth) [id=1 id_str=]
-------------------------
root@pea:~# dhclient ath0
There is already a pid file /var/run/dhclient.pid with pid 10526
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:11:f5:61:7a:12
Sending on LPF/ath0/00:11:f5:61:7a:12
Sending on Socket/fallback
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPNAK from 192.168.1.1
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
DHCPOFFER from 192.168.1.1
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.105 -- renewal in 39332 seconds.

And finally my wpa_supplicant network block for that SSID:

network={
  ssid="WAVES Wireless - Framework N02"
  key_mgmt=NONE
}

Again, if I can be any more help please let me know.

See original description
Revision history for this message
adolfotregosa (adolfotregosa) wrote :

I have exactly the same problem. Have to manually connect but on my case i'm using wep.

Revision history for this message
Andreas John (derjohn) wrote :

Hello,
the same occurs here after dist-upgrading Gutsy to version of yesterday night. With the old version it more or less worked, but sometimes I needed to click on the network 2-3 times ... then the connection became ready (100%). I am using a kernel from vanilla sources + madwifi + whoopie disk_protect patch on a Thinkpad X60s.

rgds,
derjohn

Chris MacDonald (chris-fourthandvine)
description: updated
Jason Straight (jason-jeetkunedomaster)
Changed in network-manager:
status: New → Confirmed
Revision history for this message
Martin Emrich (emme) wrote :

Same here on a Thinkpad T41p with Atheros AR5212 and current hardy. Connecting with wpa_supplicant/dhclient works fine.

Revision history for this message
Ben Wilber (benwilber) wrote :

Confirmed on Hardy Alpha 6 on MacBook Core Duo.

02:00.0 Ethernet controller: Atheros Communications, Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)

NetworkManager just churns with same output as above. Manually setting the network in /etc/network/interfaces and wpa_supplicant works though.

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Confirmed on Thinkpad T61p

Linux t61p 2.6.24-12-generic #1 SMP Sat Mar 8 02:29:24 UTC 2008 i686 GNU/Linux

network-manager 0.6.6-0ubuntu1

  *-network
       description: Wireless interface
       product: AR5212 802.11abg NIC
       vendor: Atheros Communications, Inc.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: wifi0
       version: 01
       serial: 00:1f:3a:1b:18:5d
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list logical ethernet physical wireless
       configuration: broadcast=yes driver=ath_pci ip=192.168.1.112 latency=0 module=ath_pci multicast=yes wireless=IEEE 802.11g

Revision history for this message
Phil Estes (estesp) wrote :

It should also be noted that this is a regression from gutsy (at least on my atheros hardware). In gutsy both NM and wpa_supplicant paths worked fine for WPA1/2, WEP, open connections to wireless networks.

In Hardy (at least alpha4-6 where I can confirm) *only* wpa_supplicant (or iwconfig if you just want an open network) works for any type of wireless connection-NM will do nothing with my wireless card, other than show me available networks and ask for keys where necessary. For potential time savings for other bug readers, the NM 0.7 pre packages offered in a PPA that didn't make Hardy offer no benefit, so don't waste your time.

Revision history for this message
Andreas Ntaflos (daff) wrote :

Same here on a Thinkpad T41p using Kubuntu Hardy Alpha 6 and a WPA2 wireless network. Manually invoking wpa_supplicant and dhclient works fine, wpa_supplicant.conf contains the following:

network = {
  proto = WPA2
  ssid = "MYSSID"
  key_mgmt = WPA-PSK
  pairwise = CCMP
  psk = "MYKEY"
  priority = 5
}

lspci: 02:02.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

Can't add more to the extensive report of the OP.

Revision history for this message
Martin Emrich (emme) wrote :

I found out that with my built-in Atheros card, I cannot connect to my university wireless network at all, neither with NM nor with dhclient/iwconfig. The connection comes up, but breaks down a few seconds later.

So back at home, I tried my good old 802.11b PCMCIA Wireless card (Prism II with hostap driver), and it connects fine to my home network (WPA) using NM.
So it seems to be more a problem of madwifi than network manager. As soon as I am back at the university, I'll try the PCMCIA card there.

Revision history for this message
Ben Wilber (benwilber) wrote :

Network Manager works fine with two other USB wifi adapters that I have, neither use madwifi. Using network-admin or manually editing the config files for wpa etc to configure the Atheros interface works however.

Seems it's a problem with Network Manager talking to the madwifi driver.

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

I think this bug is a regression caused by the package update described in Bug #197538.

NetworkManager 0.6.5 works fine with my internal atheros card. With 0.6.6, it won't associate with any access point. Using iwconfig on the command line, wireless works fine.

I went through the change log and there were a lot of changes to the package between 0.6.5 and 0.6.6, including a number of dropped patches. I wonder if one of those might be causing this problem?

Alexander?

Also, there's no "Importance" to this bug set yet. This is a disappointing regression in my opinion.

Revision history for this message
Andreas Ntaflos (daff) wrote :

It's still a month or so before Hardy will be released so hopefully this bug will get the attention it needs. No need to be disappointed just yet :)

Revision history for this message
Martin Emrich (emme) wrote :

So today I tried it with with our university network. With NM, neither the Atheros nor the Prism card worked. With iwconfig/dhclient, only the prism worked, but not the Atheros.

Revision history for this message
Jason Straight (jason-jeetkunedomaster) wrote :

I'm not sure if it's network-manager or wpa_supplicant's fault, but it seems that it IS telling ath0 to associate with the network but no network key is ever set. if you iwconfig while it's trying to associate you'll see it set to the correct ssid, but enc remains empty.

My guess is that since calling wpa_supplicant from the command line works it's how network-manager is calling wpa_supplicant that's the problem.

Revision history for this message
Kieran Hogg (xerosis) wrote : Re: [Bug 199802] Re: [madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to wireless network

It can't be wpa_supplicant's fault as I see the same issue connecting
to a WEP network.

Revision history for this message
Dustin Kirkland  (kirkland) wrote : Re: [Bug 199802] Re: [madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to wireless network

Agreed, I have the same problem on both WEP and open access points.
Command iwconfig-iness works. Through NetworkManager, no dice.

Revision history for this message
Johannes Ritzinger (johannes-ritzinger) wrote :

I droped off my encryption for a short time, to test wether I could connect without encryption. It still doesn't work.
I'm using a T41p.

Revision history for this message
Phil Estes (estesp) wrote :

We probably don't need too much more guessing about whether it's network manager or wpa_supplicant, etc.. for those who are reporting similarity to the original reporter the following experience is the common bond:
- *can* connect using Atheros h/w to a protected or unprotected network using non-Network Manager tools
- *cannot* connect using Atheros h/w to a protected or unprotected network using Network Manager

It's as simple as that--and if you have yet-another-experience, Ubuntu devs will usually ask you to open another bug so it can be dealt with as a different issue..that makes these bugs less cluttered with commentary of why someone does or doesn't experience the same thing as the reporter. Bottom line: different experience probably means, open a different bug.

I think the fact that 0.6.5-gutsy-era NM works and 0.6.6-hardy-era NM doesn't work is another good data point mentioned--since if you look at prior bugs in this space you notice a lot of monkeying with timeouts, and the original reporter's log from NM shows auth timeouts, it might be good to look at that area of changes in 0.6.5 to see if 0.6.6 isn't carrying the same changes that Alexander put into 0.6.5. But, this is where we need some dev. input or someone who is willing to look into the timeout issue with 0.6.6 and compare to 0.6.5. If I get some free time I might do some code inspection in this area, but it may not be until next week.

Revision history for this message
Alexander Sack (asac) wrote :

please test if the bzr branch i just associated with this bug fixes this ath_pci issue for you.

To build:

 1. get the branch
 2. build using debuild -b

To test:

 1. install libnm-*.deb and network-manager*.deb produced by the build
 2. test to connect to wpa ... test to reboot ... and so on.

Thanks,
 - Alexander

Revision history for this message
Phil Estes (estesp) wrote :

Yes--your patch fixes the issue--I'm back to the functionality I had in gutsy where NM can manage my wireless network connections (successfully). I believe I had seen that mentioned elsewhere--that madwifi isn't supporting wext very well--so your patch makes sense that it resolves the issue.

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

On Mon, 2008-03-17 at 10:42 +0000, Alexander Sack wrote:
> please test if the bzr branch i just associated with this bug fixes this
> ath_pci issue for you.

I built and installed these and they worked perfectly for me.

:-Dustin

Revision history for this message
Elliot Murphy (statik) wrote :

This works great for me on my 3rd gen MacBookPro running with madwifi. Thanks!

Revision history for this message
Chris MacDonald (chris-fourthandvine) wrote :

Built and tested Alexander's branch this morning and after a reboot everything's back to normal. Network-Manager connects as expected to my WPA network at home and my open network at school.

Thanks Alexander!

Revision history for this message
Martin Emrich (emme) wrote :

The patched network-manager works fine here, too (WPA protected network at home). I still have to reload ath_pci after resume, but this has nothing to do with this bug. Thanks!

Alexander Sack (asac)
Changed in network-manager:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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