Key annoyance

[Valentine Sinitsyn]

Hi,

> 	I was hoping for this bug to be somehow fixed in 0.1, but it's
> still here. 
> 	Sometimes, when I am trying to connect to the network,
> after already beeing associated with AP but having the dhcp negotiation
> not finalized for some longer time ( 'DHCP daemon state is now 7
> (unknown) for interface ath0' in logs), I am asked for the key. I
> guess it assumes the password I entered earlier is incorrect and I
> understand this behaviour.  As I found out, the reason for this dhcp
> negotiation taking too long is bad signal level.
> 	Anyway, since I am sure the key is correct I try to
> reconnect by clicking on the network name on the list again. What I
> can't understand is why am I beeing immediately asked for the key? This
> is wrong, as I want another connection attempt, not to enter another
> key. Knetworkmanager won't stop asking for the key like this until I
> restart it. I think that when it asks the user for
> new key and it's not beeing given such (i.e. user closes the windows)
> it should assume the key is correct and not ask for it again.
I guess this question is better to be asked for NetworkManager 
developers - KNM does nothing more than presenting you dialogs on its 
behalf. But, as I was [re]implementing key re-requesting scheme for KNM, 
let me give you some advices:
  - First of all, make sure you use NM 0.6.4 or cvs HEAD - earlier 
versions ask you for a new key every time acquiring address via DHCP 
fails. 0.6.4 upward employ more clever scheme but it also fails sometimes.
- The reason for "forgetting" key when you press Cancel button is that 
in this case KNM sends GetKeyError message to NM daemon which is also 
used to indicate error conditions like "unable to load a key from 
Wallet/Gnome keyring, please enter it again". This thing annoys me also 
but until there will be no way to distinguish between Cancel butotn and 
error, this is only reasonable behavior. As a workaround, you can reopen 
  KNM - this would help. A better solution would be filing a bug in the 
NM Bugzilla, I guess.

> PS. Even more annyoing is the fact that turning the NM stuff off,
> setting the key & essid manually via iwconfig, and then doing dhclient
> ath0 worked like a charm...
Sure. And that is what surprises me. All: could dhcdbd be an issue?

Take care,
Valentine