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:
/* 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?
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: [EMAIL PROTECTED]
| 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
