Hi,
On Thu, 2014-09-18 at 08:57 +0000, Thiemo van Engelen wrote:
> We however have problems with the wifi connection, especially when it
> is installed such that the wifi connection is marginally stable (and
> there is no ethernet connection)
> What we see is that when the connection is dropped (due to bad
> reception for example), connman tries to reconnect which can fail, in
> which case connman goes into the "failure" state with one of 2 errors:
> "connect-failed" or "invalid-key".
This depends on what wpa_supplicant actually reports back to ConnMan. My
guess is that the connection was broken in the middle of the key
exchange or similar in the second case.
> What we also see is that connman does not try to reconnect, once it is
> in the failure state. I would say that this is not the behaviour you
> would want from an embedded device, as connman would need some
> "attention" to come out of the failure state and retry.
The other side of the coin is that if we do not disable retries to a
failed network, we'd end up constantly banging on the network whenever
we have a wrong passphrase or bad reception as in your case. This will
lock out ConnMan from certain set of networks that allow only a limited
amount of connection attempts. And since those access points put the
ConnMan device on hold for quite a few hours before allowing further
(re)connects, it's quite a mess.
> When I look at my (android) phone, it retries to connect to my home
> WIFI for example, even when I am at the edge of the router range. I
> certainly never have to go into the WIFI menu because it is in some
> failure state.
> What is the reasoning behind this "failure" behaviour of connman and
> can it perhaps be adjusted via the configuration?
> Or is this typically solved in the controlling application on embedded
> devices and if this is the case, does anyone have some pointers and
> what and what not to do to get it going again without user
> interaction?
It is solved if the network is timed out by wpa_supplicant. At that
point all temporary knowledge of the network and its state is cleared
from ConnMan. Once it re-appears, it won't have any previous failed
state associated with it and can be retried.
When there is at least some form of UI, the user can always mitigate the
issue by forcefully connecting to the failed network.
Cheers,
Patrik
_______________________________________________
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman
