Hello all, We have a an embedded linux device that contains wpa_supplicant 2.2 and connman 1.25 to handle ethernet and wifi connections. This device is typically setup once and then gets very little attention and is often even hard to reach.
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". My first question is if this is known behaviour that it can fail with both of these errors? I would only expect "connect-failed" when the passphrase is correct. 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. 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? Thanks in advance. Regards, Thiemo van Engelen _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
