Knetworkmanager not saving WEP key

Just installed ( retail ) 10.1 on a sony vaio ( vgn-fe11h )

It uses ipw3956 and it all worked out the box ( except that the
installer didn't install ipw3945d )

knetworkmanager connect fine to my wlan with WEP, but for the life of
me, I can't figure out how to get it to store the wep key - I have to
enter it after every reboot.

I have read the notes on
http://websvn.kde.org/trunk/kderevie...13&view=markup
and although it says that the key should be stored, it doesn't seem to be.

Can anyone help?

--
Clive

Clive Eisen wrote:

> Just installed ( retail ) 10.1 on a sony vaio ( vgn-fe11h )
>
> It uses ipw3956 and it all worked out the box ( except that the
> installer didn't install ipw3945d )
>
> knetworkmanager connect fine to my wlan with WEP, but for the life of
> me, I can't figure out how to get it to store the wep key - I have to
> enter it after every reboot.
>
> I have read the notes on
>
http://websvn.kde.org/trunk/kderevie...13&view=markup
> and although it says that the key should be stored, it doesn't seem to
> be.

Go into YaST>Network Devices and configure the card there. Then it will
remember the key.

Malke
--
It is very dark. You are likely to be eaten by a grue.

Malke wrote:
> Clive Eisen wrote:
> http://websvn.kde.org/trunk/kderevie...13&view=markup
>> and although it says that the key should be stored, it doesn't seem to
>> be.
>
> Go into YaST>Network Devices and configure the card there. Then it will
> remember the key.
>

No doubt - but I have one wireless network at work and one at home - so
I want knetworkmanager to work as advertised i.e for it to remember
networks so that I can go from home to work and it will just happen -
like 'doze does

Clive Eisen wrote:

> Malke wrote:
>> Clive Eisen wrote:
>>
http://websvn.kde.org/trunk/kderevie...13&view=markup
>>> and although it says that the key should be stored, it doesn't seem
>>> to be.
>>
>> Go into YaST>Network Devices and configure the card there. Then it
>> will remember the key.
>>
>
> No doubt - but I have one wireless network at work and one at home -
> so I want knetworkmanager to work as advertised i.e for it to remember
> networks so that I can go from home to work and it will just happen -
> like 'doze does

I'm sorry to hear that the Network Manager doesn't work like that. I was
hoping it did. I just set up 10.1 on the laptop yesterday where,
naturally, I only have one wireless network to which I want to connect.

One way people were getting around this in older SUSEs was to set up
different profiles with SCPM. The module is in YaST under
System>Profile Manager. I haven't done this so I don't have any details
about how it works. If you try it, it would be great if you'd post your
results.

Malke
--
It is very dark. You are likely to be eaten by a grue.

Malke wrote:
> Clive Eisen wrote:
>
>> Malke wrote:
>
> I'm sorry to hear that the Network Manager doesn't work like that. I was
> hoping it did. I just set up 10.1 on the laptop yesterday where,
> naturally, I only have one wireless network to which I want to connect.
>
> One way people were getting around this in older SUSEs was to set up
> different profiles with SCPM. The module is in YaST under
> System>Profile Manager. I haven't done this so I don't have any details
> about how it works. If you try it, it would be great if you'd post your
> results.

more on this - looking at http://www.ces.clemson.edu/linux/nm.shtml
networkmanager should use gnome-keyring to store the WEP key and indeed
/opt/gnome/bin/gnome-keyring-daemon is running as my user
however strace'ing both knetworkmanager and gnome-keyring shows that
knetworkmanager never calls keyring.

I guess I have done something to prevent this - any ideas?

TIA
--
Clive

Clive Eisen wrote:

> Malke wrote:
>> Clive Eisen wrote:
>>
>>> Malke wrote:
>>
>> I'm sorry to hear that the Network Manager doesn't work like that. I
>> was hoping it did. I just set up 10.1 on the laptop yesterday where,
>> naturally, I only have one wireless network to which I want to
>> connect.
>>
>> One way people were getting around this in older SUSEs was to set up
>> different profiles with SCPM. The module is in YaST under
>> System>Profile Manager. I haven't done this so I don't have any
>> details about how it works. If you try it, it would be great if you'd
>> post your results.
>
> more on this - looking at http://www.ces.clemson.edu/linux/nm.shtml
> networkmanager should use gnome-keyring to store the WEP key and
> indeed /opt/gnome/bin/gnome-keyring-daemon is running as my user
> however strace'ing both knetworkmanager and gnome-keyring shows that
> knetworkmanager never calls keyring.
>
> I guess I have done something to prevent this - any ideas?

I wish I did. As I said (or maybe I didn't ;-) ), I installed my Atheros
card by following various advice from people on this group. After the
driver was installed, Network Manager popped up and found my wireless
network. I entered the key and was on line. However, NM kept asking for
the key so I went into YaST and configured the wireless adapter which
now showed up in Network Devices properly as ath0 (only the ethernet
adapter had been there before). And I haven't had a problem since.
Since I haven't tried to connect to any wireless networks but my own, I
can't add to that.

I looked at the website you linked to, and it is very interesting. I
never got a call from Gnome Keyring when I set up my wireless. I run
KDE. So maybe this is handled differently on SUSE? I'm really sorry I
don't have any answers for you. Maybe someone who knows will come
along.

Malke
--
"I have a cunning plan..."

Malke wrote:
> Clive Eisen wrote:
>
>> Malke wrote:
>>> Clive Eisen wrote:
>>>
>>>> Malke wrote:

> I looked at the website you linked to, and it is very interesting. I
> never got a call from Gnome Keyring when I set up my wireless. I run
> KDE. So maybe this is handled differently on SUSE? I'm really sorry I
> don't have any answers for you. Maybe someone who knows will come
> along.
>
> Malke

Aha - it all just works!

make sure you are running KDEWallet and under settings/configure wallet
you have ticked 'Enable the KDE wallet subsystem'

Now it all works as advertised. - click on a previously visited wireless
network in KNetowrkmanager and bingo - it just connects!

Clive Eisen wrote:

> Malke wrote:
>> Clive Eisen wrote:
>>
>>> Malke wrote:
>>>> Clive Eisen wrote:
>>>>
>>>>> Malke wrote:
>
>> I looked at the website you linked to, and it is very interesting. I
>> never got a call from Gnome Keyring when I set up my wireless. I run
>> KDE. So maybe this is handled differently on SUSE? I'm really sorry I
>> don't have any answers for you. Maybe someone who knows will come
>> along.
>>
>> Malke
>
> Aha - it all just works!
>
> make sure you are running KDEWallet and under settings/configure
> wallet you have ticked 'Enable the KDE wallet subsystem'
>
> Now it all works as advertised. - click on a previously visited
> wireless network in KNetowrkmanager and bingo - it just connects!

Ooh! That's great information! Thank you *so* much for posting this. I
think I have KDEWallet enabled but I don't remember. I'll definitely
check it out the next time I turn on the laptop.

Thanks again for sharing, and I'm glad you got it solved.

Malke
--
It is very dark. You are likely to be eaten by a grue.