NetworkManager and iwp3945 Driver WPA/Hidden Network

[David Roth]

Can not connect to my network which is hidden (SSID Broadcast off) and encryption set to WPA. knetworkmanager keeps prompting me to change my pre-shared key.

uname -r: 2.6.22-8-generic
dmesg|grep 3945: ipw3945: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.1mp
dmesg|grep ieee80211 : ieee80211: 802.11 data/management/control stack, git-1.1.13

tail -f /var/log/syslog|grep NetworkManager (During connection to my wireless network):

Jul 22 23:32:23 l1-k NetworkManager: <debug> [1185165143.711176] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'wlan1'
Jul 22 23:32:23 l1-k NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/eth3 / wlan1
Jul 22 23:32:23 l1-k NetworkManager: <info> Deactivating device eth3.
Jul 22 23:32:23 l1-k NetworkManager: <info> Device eth3 activation scheduled...
Jul 22 23:32:23 l1-k NetworkManager: <info> Activation (eth3) started...
Jul 22 23:32:23 l1-k NetworkManager: <info> Activation (eth3) Stage 1 of 5 (Device Prepare) scheduled...
Jul 22 23:32:23 l1-k NetworkManager: <info> Activation (eth3) Stage 1 of 5 (Device Prepare) started...
Jul 22 23:32:23 l1-k NetworkManager: <info> Activation (eth3) Stage 2 of 5 (Device Configure) scheduled...
Jul 22 23:32:23 l1-k NetworkManager: <info> Activation (eth3) Stage 1 of 5 (Device Prepare) complete.
Jul 22 23:32:23 l1-k NetworkManager: <info> Activation (eth3) Stage 2 of 5 (Device Configure) starting...
Jul 22 23:32:23 l1-k NetworkManager: <info> Activation (eth3/wireless): access point 'wlan1' is encrypted, and a key exists. No new key needed.

[David Roth (davidroth)]

If you haven't guessed, I am using KDE /w Gutsy/Tribe 3

[David Roth (davidroth)]

I could be wrong, but I don't think this is a knetworkmanager issues. I believe it belongs to NetworkManager. What do you guys think?

[sk0rp10 (matteo-andreozzi)]

I can confirm this bug, but this is not related to a hidden network.
Instead, while the ipw3945 is performing the auth handshake to install a WPA connection,
Knetworkmanagers times out the connection, wrongly thinking it has failed the authentication, and
requesting a new authentication key.

If u say Cancel to the new key request and then reconnect you'll see the green led of ipw3945 has just becomed stable green , which means
connected, and knetworkmanager will suddenly start the dhcp procedure because it founds the wireless link has already been established.

I think this could be easly fixed just setting a longer timeout for ipw3945 wireless cards, which are slower in joining wpa networks, maybe due to the fact they have a separate running daemon service which helps the kernel module , maybe slowing down the driver itself.

[David Roth (davidroth)]

Can you post the syslog after you go though the procedure you described above. When I do what you suggested (hitting cancel after key request), I do get a solid light, but I still cannot connect. As a matter of fact, the iwconfig doesn't even show my network SSID. Here is mine:

Jul 24 17:29:06 gutsy NetworkManager: <debug> [1185316146.578599] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'wlan1'
Jul 24 17:29:06 gutsy NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / wlan1
Jul 24 17:29:06 gutsy NetworkManager: <info> Deactivating device eth1.
Jul 24 17:29:06 gutsy dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason
Jul 24 17:29:06 gutsy NetworkManager: <info> Device eth1 activation scheduled...
Jul 24 17:29:06 gutsy NetworkManager: <info> Activation (eth1) started...
Jul 24 17:29:06 gutsy NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jul 24 17:29:06 gutsy NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jul 24 17:29:06 gutsy NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jul 24 17:29:06 gutsy NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jul 24 17:29:06 gutsy NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jul 24 17:29:06 gutsy NetworkManager: <info> Activation (eth1/wireless): access point 'wlan1' is encrypted, and a key exists. No new key needed.
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: sending command 'INTERFACE_ADD eth1^I^Iwext^I/var/run/wpa_supplicant^I'
Jul 24 17:29:06 gutsy kernel: [ 719.104000] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: response was 'OK'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: sending command 'AP_SCAN 2'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: response was 'OK'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: response was '0'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 776c616e31'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: response was 'OK'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 scan_ssid 1'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: response was 'OK'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 proto WPA'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: response was 'OK'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: response was 'OK'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 psk <key>'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: response was 'OK'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jul 24 17:29:06 gutsy NetworkManager: <info> SUP: response was 'OK'
Jul 24 17:29:06 gutsy NetworkManager: <info> Activation (eth1) Stag...

[David Roth (davidroth)]

And by the way I did a complete wipe and reinstall of Gutsy/Tribe 3

[Kansei (clauretano)]

Ok, so as it turns out this isn't exactly the same issue as but #64173 ..I guess that bug covers my ThinkPad T42 but this bug covers my Latitude D620..

I too can confirm that pressing cancel makes the light go steady (but with no usable connection).

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

This is a Network Manager bug.
Fix released for Hardy.

Marking as duplicate.
Any backport requests should be first examined against:
https://help.ubuntu.com/community/UbuntuBackports
Then filed against the main bug stream. Unless this duplicate message is viewed as errant. In which case please un-duplicate.