WPA - network-manager keeps asking for password

Bug #131233 reported by mon
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

Hi

I have a wpa personal wifi connection at home. In gutsy, whenever I logg in, it asks for the password. I type it, it asks me to save it in the keyring, and asks me to enter a key for the keyring. After doing that I can stablish a connection, but if I logg out I have to repeat the whole process.

thanks

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

which package version are you using?

Changed in network-manager:
status: New → Incomplete
Revision history for this message
mon (javiermon-deactivatedaccount) wrote :

$ apt-cache policy network-manager
network-manager:
  Instalados: 0.6.5-0ubuntu9
  Candidato: 0.6.5-0ubuntu9
  Tabla de versión:
 *** 0.6.5-0ubuntu9 0
        500 http://archive.ubuntu.com gutsy/main Packages
        100 /var/lib/dpkg/status

$ apt-cache policy gnome-keyring
gnome-keyring:
  Instalados: 2.19.6.1-0ubuntu2
  Candidato: 2.19.6.1-0ubuntu2
  Tabla de versión:
 *** 2.19.6.1-0ubuntu2 0
        500 http://archive.ubuntu.com gutsy/main Packages
        100 /var/lib/dpkg/status
javier@macbook:~$

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

This looks like a duplicate of bug #36651, marked as a duplicate

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

lets keep this bug wpa specific (don't merge with wep bugs)

Revision history for this message
Oleksij Rempel (olerem) wrote :

i still have some problems with wpa. at the momment ( August 31 2007, after update ) it sort of connected to AP.
Reality: it connected to wired networkc and trying to connect to wifi
nm report: connected to wifi but no signal, no wired network

ifconfig:
eth0 Protokoll:Ethernet Hardware Adresse 00:16:41:22:22:22
          inet Adresse:192.168.0.152 Bcast:192.168.0.255 Maske:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1528 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1175 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:1215114 (1.1 MB) TX bytes:157848 (154.1 KB)
          Interrupt:18

eth1 Protokoll:Ethernet Hardware Adresse 00:13:CE:44:44:44
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:3292 errors:19 dropped:19 overruns:0 frame:0
          TX packets:645 errors:0 dropped:0 overruns:0 carrier:1
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:1640 (1.6 KB) TX bytes:4842 (4.7 KB)
          Interrupt:23 Basisadresse:0x4000 Speicher:90301000-90301fff

eth1:avah Protokoll:Ethernet Hardware Adresse 00:13:CE:44:44:44
          inet Adresse:169.254.5.23 Bcast:169.254.255.255 Maske:255.255.0.0
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          Interrupt:23 Basisadresse:0x4000 Speicher:90301000-90301fff

lo Protokoll:Lokale Schleife
          inet Adresse:127.0.0.1 Maske:255.0.0.0
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:100 (100.0 b) TX bytes:100 (100.0 b)

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 131233] Re: WPA - network-manager keeps asking for password

On Fri, Aug 31, 2007 at 07:38:12PM -0000, fishor wrote:
> i still have some problems with wpa. at the momment ( August 31 2007, after update ) it sort of connected to AP.
> Reality: it connected to wired networkc and trying to connect to wifi
> nm report: connected to wifi but no signal, no wired network

please provide the output of

  # iwconfig eth1

as well as

  # sudo iwlist scan

when you are in the situation you describe.

Thanks,

 - Alexander

Revision history for this message
Mike (mike0999) wrote :

I have the same problem when using gutsy in persistent mode from a usb stick. I know persistence has been broken, but I have been thinking this failure of gnome network manager to maintain the key might be a different issue because some of the persistent functionality in gutsy has actually worked for me.

Note, I believe some people may have experienced this same network manager issue in the patched feisty iso that was prepared in which persistence worked. Don't know if that was the same problem as this one (particularly if normal (non live-cd) feisty installations didn't experience this problem. But, I wanted to mention that in case it is possible this issue was introduced by changes back in feisty (don't know if that might help in the trouble shooting).

Alexander, it might be intersting to see if your problem persists with the feisty version of gnome network manager and, if it does, with the edgy version of network manager. You could revert to each of these by creating a preferences file in your /etc/apt directory and pinning gnome network manager at the feisty and edgy versions of the gnome network manager, respectively. (Don't know if they will be compatible, but you might try if you have time. I might try that as well).

Revision history for this message
Mike (mike0999) wrote :

Hmm. I reverted to the feisty version of network-manager (0.6.4-6ubuntu7) and to the feisty version of network-manager-gnome (0.6.4-6ubuntu7), and the network manager now seems to be remembering my WPA key on a persistent liveUSB drive. So, maybe there was no issue with feisty. Maybe this issue was introduced in the gutsy changes.

Revision history for this message
Oleksij Rempel (olerem) wrote :

it seems like NM hase srror and can't go back in normal state... to
reproduce this i tryed to connect AP two time. first time it asked a
password conectetd and _sort of_ swithced to wired network, second time
it connected and indicated "no signal" but didn't swiched to wire.

one more problem was today with NM. after boot it didn't get to connect
dhcp network... but static ip working well. so now switch button show
only wlan as choice no lan.

> # iwconfig eth1

lo no wireless extensions.

eth0 no wireless extensions.

eth1 unassociated ESSID:""
          Mode:Managed Frequency=2.457 GHz Access Point: Not-Associated
          Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
          Retry limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality:0 Signal level:0 Noise level:0
          Rx invalid nwid:0 Rx invalid crypt:3 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

irda0 no wireless extensions.

> # sudo iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
          Cell 01 - Address: 00:60:B3:99:99:99
                    ESSID:"elm"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:10
                    Frequency:2.457 GHz (Channel 10)
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                              11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Quality=72/100 Signal level=-48 dBm
                    IE: WPA Version 1
                        Group Cipher : WEP-40
                        Pairwise Ciphers (1) : WEP-40
                        Authentication Suites (1) : PSK
                    Extra: Last beacon: 916ms ago

irda0 Interface doesn't support scanning.

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 131233] Re: WPA - network-manager keeps asking for password

On Sat, Sep 01, 2007 at 06:53:13AM -0000, Mike wrote:
> Hmm. I reverted to the feisty version of network-manager
> (0.6.4-6ubuntu7) and to the feisty version of network-manager-gnome
> (0.6.4-6ubuntu7), and the network manager now seems to be remembering my
> WPA key on a persistent liveUSB drive. So, maybe there was no issue
> with feisty. Maybe this issue was introduced in the gutsy changes.
>

How did you do that? just downgrading those packages? or did you
rebuild them in gutsy?

 - Alexander

Revision history for this message
mon (javiermon-deactivatedaccount) wrote :

FYI this no longer happens here.

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

fixed for reporter.

Changed in network-manager:
status: Incomplete → Fix Released
Revision history for this message
Wiktor Stasiak (wiktor-stasiak) wrote :

Same situation on Intrepid.

I am using WPA2-Personal PSK authentication. Every time I connect to network I need to enter password (WEP passwords saves without any problem).
Password is alpha-numeric with "/" inside (if this is helpful).
My wifi card is Intel 4965 AGN

Package version:
$ apt-cache policy network-manager
network-manager:
  Installed: 0.7~~svn20080908t183521+eni0-0ubuntu3
  Candidate: 0.7~~svn20080908t183521+eni0-0ubuntu3
  Version table:
 *** 0.7~~svn20080908t183521+eni0-0ubuntu3 0
        500 http://pl.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

Changed in network-manager:
status: Fix Released → Incomplete
Revision history for this message
Alan Cramer (alan.cramer) wrote :

confirmed on my eeepc 900 running intrepid. Continually asks for password upon boot.

Revision history for this message
mogwai (scruffy-mogwai) wrote :

Confirmed. Currently running Intrepid Beta from a USB hard drive.
Always have to re-enter WPA key after login.

apt-cache policy network-manager
network-manager:
  Installed: 0.7~~svn20081018t105859-0ubuntu1
  Candidate: 0.7~~svn20081018t105859-0ubuntu1
  Version table:
 *** 0.7~~svn20081018t105859-0ubuntu1 0
        500 http://archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

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.