On Wed, Sep 17, 2008 at 6:35 AM, Dan Williams <[EMAIL PROTECTED]> wrote: > On Tue, 2008-09-16 at 14:49 +0200, Pablo Martí wrote: >> Hi all, >> >> as a part of a project, we want to export a new method for NM, a >> "RescanAccessPoints" that refreshes the AP list. We've tried to export >> nm_supplicant_interface_request_scan, but it doesnt seems to work. >> Somehow two signals "scan-result" and "scanned-ap" seem to be involved >> with the scan process, but when we force it with the mentioned method >> only the "scan-result", but no "scanned-ap" signal is emitted... are >> we in the right track? Any hints would be really appreciated. > > Honestly, don't do this. It comes up again and again and is in the > archives. Instead, we should be optimizing the scan algorithm. There > isn't a good reason to force a rescan if (a) the drivers don't suck and > (b) the NM scan algorithm is optimal.
Sorry for the noise, it seems that (a) was the culprit here. We are using atheros and in our testing a "gone" AP would still appear after more than 6/7min with iwlist (as root). Ndiswrapper + broadcom notices instantaneously that the AP is gone. Pablo -- Pablo Martí http://www.linkedin.com/in/pmarti || http://www.warp.es python -c "print '706d6172746940776172702e6573'.decode('hex')" _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
