[ralink] nm-applet will not keep a WPA key.

[brummie]

It just doesn't keep the WPA key after rebooting. This means i have to log on and put in the WPA key before anyone else can use the computer.
I could share the WPA key with the users but that compromises security.

[syslog contains this:
Oct 9 09:32:42 ubuntu kernel: [47851.053106] wlan0: RX WEP frame with unknown keyidx 2 (A1=ff:ff:ff:ff:ff:ff A2=00:16:b6:xx:xx:xx A3=00:15:c5:xx:xx:xx)
Oct 9 09:32:42 ubuntu kernel: [47851.225570] wlan0: RX deauthentication from 00:16:b6:xx:xx:xx (reason=15)
--Paul ]

[brummie (brummie-brummie)]

DOH forgot to say:

Gutsy gibbon, completely updated.
Using WMP54G ver4.1 PCI RALINK RT2561/RT61 card

[Alexander Sack (asac)]

please attach your /var/log/syslog.
Thanks,
 - Alexander

[brummie (brummie-brummie)]

Syslog added

[Alexander Sack (asac)]

what configuration is set in gconf (open Alt+F2 -> gconf-editor -> search for network and/or wireless) for that device/network?

[brummie (brummie-brummie)]

here is a screen grab of it.

Wierdly for the first time ever i just logged in and it remembered the settings.
Going to reboot now and see if it does t again.

[brummie (brummie-brummie)]

No not this time and the last time i was wrong too. I had it set for non roaming but it wouldnt work so when i clicked allow roaming it logged straight in.

This is the 3rd install of ubuntu GG that does this.

[Shadows_Friend (shadows-friend)]

If the issue appears while not using roaming mode, i.e. putting the data in the System -> Administration -> Network -> interface mask and not the network manager applet I can confirm this. This is pretty annoying if you want to use for example a static ip configuration. I use a Intel Corporation PRO/Wireless 2915ABG device with the ipw2200 driver.

[brummie (brummie-brummie)]

UPDATE:

if i click on the nm-applet and select the WAP i want to log onto during the initial boot everything ifs fine.
If i just leave it it will never connect to my prefered, even if its the only one on the list.

Its really really annoying :(

[brummie (brummie-brummie)]

Update:

If you click more than once it can freeze the desktop

[Paul Dufresne (paulduf)]

Marking as Confirmed (was Incomplete).
A duplicate of bug #140422 ? (question asked to developer)

[Kristian Kißling (kkissling)]

Confirm for ipw3945, Ubuntu 7.10, same behaviour here. Maybe it has to do with the lenght of the key (since it worked before, when I used a shorter keyword)?
Before: 11 only characters
Now: 13 including numbers

Just a wild guess :)

Regards
Kristian

[Kristian Kißling (kkissling)]

From /var/log/syslog

Aug 29 21:33:09 slurm NetworkManager: <info> eth1: link timed out.
Aug 29 21:33:09 slurm NetworkManager: <info> SWITCH: found better connection 'eth1/pi' than current connection 'eth1/pi'. same_ssid=1, have_link=0
Aug 29 21:33:09 slurm NetworkManager: <info> Will activate connection 'eth1/pi'.
Aug 29 21:33:09 slurm NetworkManager: <info> Device eth1 activation scheduled...
Aug 29 21:33:09 slurm NetworkManager: <info> Deactivating device eth1.
Aug 29 21:33:09 slurm dhclient: There is already a pid file /var/run/dhclient.eth1.pid with pid 6978
Aug 29 21:33:09 slurm dhclient: killed old client process, removed PID file
Aug 29 21:33:09 slurm dhclient: DHCPRELEASE on eth1 to 192.168.0.1 port 67
Aug 29 21:33:09 slurm avahi-daemon[5335]: Withdrawing address record for 192.168.0.171 on eth1.
Aug 29 21:33:09 slurm avahi-daemon[5335]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.0.171.
Aug 29 21:33:09 slurm avahi-daemon[5335]: Interface eth1.IPv4 no longer relevant for mDNS.
Aug 29 21:33:10 slurm NetworkManager: <info> Activation (eth1) started...
Aug 29 21:33:10 slurm NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Aug 29 21:33:10 slurm NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Aug 29 21:33:10 slurm NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Aug 29 21:33:10 slurm NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Aug 29 21:33:10 slurm NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Aug 29 21:33:10 slurm NetworkManager: <info> Activation (eth1/wireless): access point 'pi' is encrypted, and a key exists. No new key needed.
Aug 29 21:33:10 slurm NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface eth1
Aug 29 21:33:10 slurm NetworkManager: <info> DHCP daemon state is now 11 (unknown) for interface eth1
Aug 29 21:33:10 slurm NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface eth1
Aug 29 21:33:11 slurm NetworkManager: <info> supplicant_interface_init() - connect to global ctrl socket (0/10).
Aug 29 21:33:11 slurm NetworkManager: <info> supplicant_interface_init() - connect to global ctrl socket (1/10).
Aug 29 21:33:11 slurm NetworkManager: <info> SUP: sending command 'INTERFACE_ADD eth1^I^Iwext^I/var/run/wpa_supplicant9^I'
Aug 29 21:33:11 slurm NetworkManager: <info> SUP: response was 'OK'
Aug 29 21:33:11 slurm NetworkManager: <info> supplicant_init() - connect to device ctrl socket (1/10).
Aug 29 21:33:11 slurm NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Aug 29 21:33:11 slurm NetworkManager: <info> SUP: response was 'OK'
Aug 29 21:33:11 slurm NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Aug 29 21:33:11 slurm NetworkManager: <info> SUP: response was '0'
Aug 29 21:33:11 slurm NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 7069'
Aug 29 21:33:11 slurm NetworkManager: <info> SUP: response was 'OK'
Aug 29 21:33:11 slurm NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 pro...

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[[e-mail] (orders-sh2515)]

I am having the same problem. I set up a computer for my parents, however they can only get on the internet if I go to their house and retype the password in for them. was thinking of doig a script for them,but that would make it quite a security risk. I am going to install 8.10 this afternoon, if that doesn't work will try stopping NetworkManager, though if that fails I may go back to wep.

[[e-mail] (orders-sh2515)]

Here is my log of the wlan1

at first I thought that it hadn't remembered if the password was in capitals or not, but it just will not use the password on start up.

[rusivi2 (rusivi2-deactivatedaccount)]

In Maverick, Network Manager successfully caches for future use and uses inputted WPA credentials. Marking as fixed but if you notice it happen please update status.

 lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10

apt-cache policy network-manager
network-manager:
  Installed: 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
  Candidate: 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
  Version table:
 *** 0.8.1+git.20100810t184654.ab580f4-0ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
        100 /var/lib/dpkg/status