Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Auto-connect from wpa_supplicant and ConnMan does not become
aware (Jose Blanquicet)
----------------------------------------------------------------------
Message: 1
Date: Mon, 2 Jan 2017 18:06:49 +0100
From: Jose Blanquicet <[email protected]>
To: [email protected]
Subject: Auto-connect from wpa_supplicant and ConnMan does not become
aware
Message-ID:
<cafc8ijlycm99n2r8c5mjjbvrt7yv0onevalxar8x3ogv_zp...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Hi,
These are the steps to replicate this issue:
1. Connect to an AP (AP1) using WPS. After this, wpa_supplicant has
new network profile on this interface marked as "Current", which is
not tracked by ConnMan as is done for WPA2 connections.
2. Disconnect from it. At this point, the network profile is still
present in wpa_supplicant but now it is inactive.
3. Try to connect to another AP (AP2) using WPS.
4. Let it go in time-out (2 min).
5. wpa_supplicant automatically re-connect to previous AP, the one
corresponding to the network profile stored after the previous
connection (AP1). The issue is that ConnMan is not aware of such a
connection thus it continue showing WiFi Technology as "Disconnected"
when it is not true any more.
I checked why it is happening and I found that actually this only
happens when first connection (Step 1) is done using WPS. It is
because when ConnMan uses WPA2, first creates a profile network
(AddNetwork() in terms of wpa_supplicant) and keeps track of it in
order to delete it after a disconnection. Instead, for WPS, it is not
created any profile network because it is automatically created by
wpa_supplicant after receiving the WPS Credentials. Therefore, when
ConnMan disconnects from AP1, it does not remove the network profile
which is later used to automatic reconnection by wpa_supplicant.
I asked if such a reconnection is a desired behaviour in wpa_supplican
mailing list and Jouni confirmed this is how it should works and
suggested a solution
(http://lists.infradead.org/pipermail/hostap/2016-December/036844.html).
He told that we need to keep track of the created network profiles
during WPS provisioning (Yes, they may be more than one) and then mark
them as disabled or delete them. What do you think?
Regards,
Jose Blanquicet
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 15, Issue 2
**************************************
