Re: Pruning the active AP

[Dan Williams <dcbw redhat com>]

On Thu, 2008-07-03 at 17:28 +0200, Markus Becker wrote:
> Hello,
> 
> I was checking how NM reacts, when an AP, that we are connected to,
> dies or is getting out of range. I was expecting NM to notice that and 
> remove the current AP from the list of available APs. However, NM keeps 
> the AP in its list. I think this is because of this in nm-device-wifi.c:

Have you tried it with the patch from Adel Gallah for the scan timeout
stuff from last week?  That patch specifically fixed the issue of never
noticing that the AP was out of range even after the supplicant had sent
the disconnection status.

> /* Don't ever prune the AP we're currently associated with */
> if (cur_ap_path && !strcmp (cur_ap_path, nm_ap_get_dbus_path (ap)))
>    keep = TRUE;
> 
> What was the reasoning behind keeping the AP we're connected to, when it 
> is not in the scanning list anymore? Are some cards not reporting the AP 
> we are connected to in the scanning list or why?

Yes, even though they technically should, drivers and cards don't
necessarily do this.  Since wireless is a fairly unreliable medium, it's
not always the case that the connected AP's beacons will show up in a
given scan.  We simply cannot rely on that unless drivers are mandated
to include that upstream in the kernel.

Dan

> Markus
> 
> ------------------------------------------------
> | Dipl.-Ing. Markus Becker
> | Communication Networks
> | Mobile Research Center
> | TZI - Center for Computing Technologies
> | University Bremen
> | Germany
> ------------------------------------------------
> | web: http://www.comnets.uni-bremen.de/~mab/
> | mailto: mab comnets uni-bremen de
> | telephone: +49 421 218 2287
> | building: NW1 room: N2260
> ------------------------------------------------
> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list