Hi, This is our scenario: 1. Connect to an AP using WPS. After this, there is a new network on this interface marked as "Current". 2. Disconnect from it. At this point, the network is still there when we do list_networks but now it is inactive. 3. Start a new WPS Session. 4. Let it go in time-out (2 min). 5. wpa_supplicant automatically re-connect to previous AP, the one corresponding to the network still present in list_networks. Is this a desired behavior? From our point of view it is not because we just previously disconnected from it, it means that we do not want to be connected to that AP. Now, the question here is, should not wpa_supplicant mark that network in such a way that it does not re-connect after user specifically asked to get disconnected? Or instead, should we remove that network after doing disconnect as we do for WPA2? Otherwise, is there another way to do it? If the correct way to avoid that behavior is by removing the network after the disconnection, how can we get the network's path? For WPA2 it is gotten because we pass through Interface.AddNetwork(). Instead, this method is not called for WPS thus we think that this could be obtained from property "CurrentNetwork" when we receive the signal Interface.PropertyChanged, of course after a "success" in signal Interface.WPS.Event. Would it be correct? Or what could you suggest us? Regards, Jose Blanquicet VISITA IL NOSTRO SITO WEB! - VISIT OUR WEB SITE! www.magnetimarelli.com Confidential Notice: This message - including its attachments - may contain proprietary, confidential and/or legally protected information and is intended solely for the use of the designated addressee(s) above. If you are not the intended recipient be aware that any downloading, copying, disclosure, distribution or use of the contents of the above information is strictly prohibited. If you have received this communication by mistake, please forward the message back to the sender at the email address above, delete the message from all mailboxes and any other electronic storage medium and destroy all copies. Disclaimer Notice: Internet communications cannot be guaranteed to be safe or error-free. Therefore we do not assure that this message is complete or accurate and we do not accept liability for any errors or omissions in the contents of this message. _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
