Hi Daniel, Patrick, et al,
This email is to try and convince you to spend some more time on the discussion that
started back in January , and ended with .
The background of the patch is this: our devices, running ConnMan, are unattended. And of
course one could argue that customers should always use Ethernet for making things robust,
but they don't. Therefore we also need our wifi setup to be as rock solid as ever
And by design that is a bit difficult with wifi, as the client can't always
distinguish between wrong password and no signal. Currently ConnMan will give up after a
few retries, on assumption that the password must be wrong and because it doesn't want
to keep retrying. Since -some- APs might block it then. I've never had my phone, nor
my laptop, forget a wifi password. And, at least before we applied the RFC-d patch, we,
and our customers, have seen ConnMan 'forgetting' the password..
So, can we reopen this discussion? Last status was:
> So that means we have three options:
> 1) connman.conf, global knob
> 2) config file no D-Bus API
> 3) D-Bus API
> All of them have their downside. Patrik what is your stand?
To me, 2) has the distinct downside of not being useful.
To me, 1) would be most simple to use, implement, document and understand. And (of course)
the default behavior should not be changed.