Server V2 & V3 auth failure handling
Everyone,
please test / audit: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/4ff5...
Server V2 & V3: suspend periodic reconnect attempts on authentication failures (incorrect credentials) to avoid blocking of shared public IP addresses (mobile network proxies/gateways). A new reconnect attempt is triggered by changing the configuration. Changing the server configuration now also automatically triggers a reconnect, and the web UI assists in tracking config change results by showing the respective status and start/stop buttons after a change.
New notifications (+ implied events): - [alert] server.v2.auth.failure -- Incorrect server V2 login credentials - [alert] server.v3.auth.failure -- Incorrect server V3 login credentials
Background of this change: users not caring about fixing their server configuration or disabling their connections after some account change or deletion are now frequently causing IP blockings from their module's repeated login failures, depending on the mobile provider in use affecting many other users due to very few shared CGNAT public IP addresses.
The most recent extreme case of this was many (most? all?) "simbase.com" customers apparently sharing a single Amazon AWS IP (35.156.18.25) when connecting via a cellular network. That IP is now blocked over and over throughout the day on my server, and the IP being in the AWS cloud forbids whitelisting, as Amazon frequently allows misuse of their infrastructure by malicious actors.
The change attempts to solve the issue at the source. Of course users not taking responsibility for their device configuration probably also ignore updates, so this will fix things only in the long run.
For anyone affected now my advice is to change the mobile provider. Good providers distribute their users across a multitude of public IP addresses.
The issue could be solved for responsible users by enabling IPv6 for the module networking. IPv6 support doesn't seem to be as simple as enabling it though -- tried that. We may also need to upgrade the ESP-IDF version, as it seems the 3.3 DHCP module doesn't really support IPv6.
Regards, Michael
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
participants (1)
-
Michael Balzer