This behavior usually points to how WireGuard binds to the source interface and endpoint at tunnel initialization. When Wi-Fi drops but the interface isn’t fully brought down, the tunnel can remain bound to the old route, so it doesn’t automatically re-establish over the mobile WAN. That’s why disabling Wi-Fi manually forces a clean rebind and makes failover work. i Suggest you add the details on Failover and Wireguard VPN mutually exclusive on RUTX50
On RUTX devices, this is often addressed by:
-
Ensuring correct routing metrics so the mobile interface becomes the preferred default route during failover
-
Using interface tracking or scripts to restart the WireGuard service when WAN priority changes
-
Verifying that WireGuard is not pinned to a specific interface or source IP
In setups where connectivity is critical and behavior needs to be demonstrated or documented (for example, recording short troubleshooting or explainer videos with motion overlays using tools like Alight Motion Mod APK), clearly visualizing interface state changes can help diagnose when and why the tunnel fails to rebind.