namely: 10266 [gnome2.26] cannot connect to wireless when selected from wireless networks list
there were some bugs in how we handled NULL BSSID selections. Mostly fixed already. 10084 Info from wlan cache is inconsistent with state of system involved updating the selected/connected values in the scandata and triggering a scan when they change. Bulk of change was adding nwamd_wlan_set_selected_connected() and calling it at appropriate times. 10377 phys showing needs selection when ip link is up. This involved propogating link state changes to IP, while not tearing down IP on a down event for WiFi. If we reconnect to a different WLAN (with a different ESSID), we set do_unplumb_on_init for the IP NCU, which will cause IP to be unplumbed before we replumb and initialize when the WiFi link comes back up. This allows us to be less destructive with IP state in cases with transient connectivity issues - i.e. where we disconnect/reconnect to a WLAN. 10334 vpn application does not stop immediately on rule condition being removed Anurag caught the reason that this happens - we don't do a full condition check unless the IP NCU has gone up/down, and this combined with the lack of propogation of link state to IP meant that conditions were not being reevaluated at the appropriate time. I've verified that the GUI works with these changes, and they also include the suggested fix for 6867906 Kernel hangs during boot in startup_bios_disk with snv_120 Thanks! Alan
