KConnectionManager: Entering WEP password every time I connect

I finally got my Intel 3945ABG WiFi chip installed (by reinstalling
SUSE 10.1 and doing an online update, which updated the Intel WiFi
packages), and it promptly burst into life, promting me for the
password. Cracked it it, I thought.

But now whenever I power the machine on it does not connect
automatically. When I click on the WiFi connection in KNetworkManager
(i.e. the one with the correct SSID) I am always prompted for the
password - which, as 26 hex digits, is a pain.

What may just be connected is that originally I was using KWallet.
With that enabling the connection always got stuck at 0%. Now I have
disabled KWallet I get the symptoms described above.

I have my laptops configured with "traditional ifup" and set my WPA keys
with YaST. For different networks and keys I use the profile manager and
select the appropriate profile at boot. One of the main reasons I chose
this is that network manager does not accept WPA-PSK. But in addition, the
wireless is brought up at boot rather than at login. This has been far
more reliable.

Mike

Ken Wheatley wrote:

> I finally got my Intel 3945ABG WiFi chip installed (by reinstalling
> SUSE 10.1 and doing an online update, which updated the Intel WiFi
> packages), and it promptly burst into life, promting me for the
> password. Cracked it it, I thought.
>
> But now whenever I power the machine on it does not connect
> automatically. When I click on the WiFi connection in KNetworkManager
> (i.e. the one with the correct SSID) I am always prompted for the
> password - which, as 26 hex digits, is a pain.
>
> What may just be connected is that originally I was using KWallet.
> With that enabling the connection always got stuck at 0%. Now I have
> disabled KWallet I get the symptoms described above.

On Fri, 13 Oct 2006 14:59:23 GMT, Ken Wheatley
<ken.wheatley@birchanger.com> wrote:


>
>But now whenever I power the machine on it does not connect
>automatically. When I click on the WiFi connection in KNetworkManager
>(i.e. the one with the correct SSID) I am always prompted for the
>password - which, as 26 hex digits, is a pain.
>
>What may just be connected is that originally I was using KWallet.
>With that enabling the connection always got stuck at 0%. Now I have
>disabled KWallet I get the symptoms described above.

Well, it's working now. KWallet is certainly implicated in that I have
now enabled it again. The odd thing is it seems to have taken 2 - 3
reboots before suddenly, to my surprise, it connected at logon without
any action by me.