Okay, I've spent some time tracing through the source code for NetworkManager. Some observations:
- The problem seems to have nothing to do with AP_SCAN 1 vs. AP_SCAN 2. I only see only place in the entire NetworkManager source that issues AP_SCAN at all (supplicant_send_network_config()), but this is not called before the user resorts to forcing a connection to a specific hidden network. - In nm_dbus_get_network_data_cb(), all of my stored hidden networks are iterated through, so they at least are being stored somewhere between NetworkManager restarts. - In nm_device_802_11_wireless_get_best_ap(), ap_list seems to be empty -- it doesn't iterate through the while loop even once, in the presence of the same hidden access point connected to previously. So without knowing much about how NetworkManager works, and without having more time to sit down and study it, I suspect that one of the following is probably true: - The allowed hidden networks are being stored incorrectly. After NetworkManager is restarted, the incorrectly stored parameters for the allowed hidden network do not match the actual network parameters, so a connection is not made. - Stored networks are not being added to the ap_list used in nm_device_802_11_wireless_get_best_ap() if they are not visible. What happens in between nm_dbus_get_network_data_cb() and nm_device_802_11_wireless_get_best_ap() that filters them out()? Hope that helps... -- Cannot manage hidden SSID with WEP https://bugs.launchpad.net/bugs/39707 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
