Daniel Wagner <wagi(a)monom.org> writes:
>>> If when connecting to a wifi network, the authentication
>>> connman draws the conclusion that the wifi password was wrong. This is a
>>> correct conclusion when wifi reception is good, but this can also occur
>>> on marginal wifi reception.
>> Could we teach ConnMan to behave differently depending on RSSI or any
>> input which indicates bad reception, e.g. the time for transaction? I
>> mean what helps you if you change from 2 to 10 and you got a good signal
> The issue that prompted this was a bad signal causing it to give up
> connecting and stay down for ever.
IIRC, the behavior to stay down after two retries is that some AP
block the client permanently if you try two often with the wrong
password. At least that is what I remember from the retry discussion.
Yes, that's a valid reason for limiting the number of retries *by default*.
I a way to remove that limitation.
> Removing the retry limit makes it
> work as well as can be expected in that situation, i.e. it connects
> often enough to do what it's supposed to do.
If I understood you correctly in your configuration you just keep retrying?
Correct. It must do this, or it simply drops offline for ever at some point.
> Now that's my reason for adding this setting. I can
> it being useful to someone else for different reasons. Is this somehow
> a bad idea? There is no change in behaviour unless users explicitly
> set a non-default value.
I think you need to find an way to address also the point I mentioned.
The lock-out thing? Don't change the default if that's a concern.
Having such an option in the main.conf is just too confusing in my
Frankly, I find all of connman too confusing. Feel free to suggest a