Re: networkmanager fails to associate (ipw3945)

[Volker Braun <volker braun physik hu-berlin de>]

In dragoran's wpa_supplicant log there is this suspicious entry somewhere
at the beginning:

Wireless event: new AP: 00:00:00:00:00:00
Added BSSID 00:00:00:00:00:00 into blacklist
State: ASSOCIATING -> DISCONNECTED

driver bug? wpa_supplicant bug? I don't see the reason for why
wpa_supplicant disconnects, but it does. Of course, it immediately tries
again and succeeeds.

But NetworkManager then ticks differently. The supplicant_timeout_cb() had
20 seconds to complete, but now it has only 8 seconds for the
link_timeout_cb.

Feb  8 13:48:49 localhost NetworkManager: <information>	SUP: sending command 'ENABLE_NETWORK 0' 
Feb  8 13:48:49 localhost NetworkManager: <information>	SUP: response was 'OK' 
Feb  8 13:48:49 localhost NetworkManager: <information>	Activation (eth1) Stage 2 of 5 (Device Configure) complete. 
Feb  8 13:48:57 localhost kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready

Comment: doesn't that mean that the link is up now?

Feb  8 13:48:59 localhost avahi-daemon[2565]: New relevant interface eth1.IPv6 for mDNS.
Feb  8 13:48:59 localhost avahi-daemon[2565]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::218:deff:fe05:f79e.
Feb  8 13:48:59 localhost avahi-daemon[2565]: Registering new address record for fe80::218:deff:fe05:f79e on eth1.

Comment: it is now 11 seconds past the start of the supplicant_timeout,
usually we wouldn't give up yet.

Feb  8 13:49:00 localhost NetworkManager: <information>	Activation (eth1/wireless): disconnected during association, asking for new key. 
Feb  8 13:49:00 localhost NetworkManager: <information>	Activation (eth1) New wireless user key requested for network 'mynet'. 

I think the heuristic DISCONNECT => need new password is wrong. We should
at least try a few times. Either wait until we have a fixed number of
disconnects, or wait until the end of the supplicant timeout even if there
are initial disconnects.

Volker