Hi,
On 09/20/2010 11:51 AM, Samuel Ortiz wrote:
this repeats forever... and I'm already connected to wifi on eth1
(broadcom-sta, "wl" driver).
That shouldn't happen, and I'm suspecting connmand is not triggering those
scans. Could you please check if wifi_scan() is called before those scans. ?
If wifi_scan() is not called, the next step would be to check what
wpa_supplicant is doing and see if it's doing passive or active scans.
This happens when you are connected to a wifi network and wpa_supplicant
fires a disconnect event (for example if you turn of the AP). This also
happens if you are connected to a wifi network that changes its security
from wpa->wpa2 or wpa2->wpa while connected.
As this disconnect is not triggered by connman, task->disconnecting is
FALSE and connman will not call "removeNetwork" on supplicant and it
will start scanning for the disconnected SSID every 5 seconds.
I've sent a patch right now to solve this issue.
[PATCH] Call remove_network() on unsolicited disconnect.
Cheers,
Samuel.
Best regards,
Lucio Maciel
_______________________________________________
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
