On Fri, 2011-08-05 at 15:05 +0200, Anders Gnistrup wrote: > Hi > > I am using networkmanager version 8.4, and I have problem undestanding the > AccessPointRemoved signal. > > I have made a connect_to_signal. > The list of accessPoint is listed and this is OK using GetAccessPoints. I > then create a connection and it connects. > I then power of the accessPoint, and waits....... In the mean time i check > the AP using the iwlist. Its not listed, so iwlist is OK. > > But why does is take so lang time for the AccessPointRemoved signal to be > triggered??
NM does not present the exact AP list that the driver returns, because that AP list is quite variable. Not all APs show up every scan, even if you haven't moved and the AP has not been powered off. NM creates a composite scan list that keeps APs for at least a few minutes after they may have dropped out of the scan list. This could be improved however, by keeping track of how many scans each AP has *not* been found in, and if that number reaches say 2 or three then clear the AP. In the best case that clears the AP more quickly, but in the worst case it'll still take 5 minutes for the AP to disappear because NM backs off periodic scans to once every 2 minutes after a while. Dan > I also get some state changes > (dbus_interface="org.freedesktop.NetworkManager.Device") stepping between > 4,5,6, in the end 9 when the AccessPointRemoved arrives. > > My personal gees is that is not a notworkmanager problem but rather a > wpasupplicant problem. > > Anders > _______________________________________________ > networkmanager-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/networkmanager-list _______________________________________________ networkmanager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
