Hi,
On Mon, 2015-02-23 at 09:41 -0500, Ernast Sevo wrote:
> I have noticed a strange case when attempting to connect to a hidden
> network that is already connected. For example, lets say we are
> already connected to hidden network and user is not aware this is the
> case. They attempt to connect to the hidden network manually and they
> are prompted for name and password. After entering the information,
> they never get a reply.
IIRC the code does not check whether the SSID and encryption method
matches an already configured service and can therefore fail.
The error path is probably taken, which is caused by the service timeout
after ~70s or so. Sometimes hidden WiFi networks have really a hard time
being detected for any number of reasons, one of the not properly
studied ones is a connect to an already connected network. Here ConnMan
relies on wpa_supplicant to get its act together and report things
correctly; it can happen that the signals coming for the already
connected network from wpa_supplicant are not interpreted correctly or
that there are no signalling for an already connected one...
> I believe connman in this case is never replying to the dbus call
> issuing the connect. Not sure what expected behaviour is, but my
> assumption would have been to reply that we are already connected. Is
> this a fair assumption?
The wifi_XXXXX_hidden service returns only after the "real" network
connected, i.e. wifi_XXXXX_YYYYY_managed_psk.
Perhaps the easiest band-aid is to match the given ssid and security
against the IDs of already known networks. One thing to re-test is to
see if the hidden wifi service reports failure after 70 or so seconds.
Cheers,
Patrik
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
