On 10/27/2016 09:09 AM, Saurav Babu wrote:
In the following scenario:
1. Device is connected to AP in non hidden mode.
2. Connection is initated to AP in hidden mode.
connman disconnects old service and tries to connect to new service. But
for connecting hidden service it first scans the hidden AP and when
network is added for hidden AP then connection is tried. In the meantime
normal AP got disconnected and was tried to autoconnect even before
hidden AP was scanned successfully.
Ideally non hidden AP should only be disconnected when hidden AP is
found in the scan list and its connection is intiated.
So the problem is that autoconnect is faster than scan,connect operation?
I am very reluctant to move the for() loop down from connect_service()
to service_connect() because it is not clear to me what the impact of it
is. If I read it correctly D-Bus initiates connection attempts wouldn't
change because the filter is just deeper down in the call change. Is it
really only the calls from autoconnect which will be blocked?
Maybe you should try to teach autoconnect not to call
__connman_service_connect() when we try to connect to a hidden AP? In my
eyes it makes more sense to teach autoconnect not to do stupid stuff
instead of blocking it somewhere else.