The Starlink connection is currently without an active subscription (I only use it when travelling) so the WAN interface in use is mobile.
I’ve upgraded to RUTX_R_00.07.15.2 and since then failover stopped working, meaning clients will not navigate internet anymore however VPN traffic (both ways) still works!
We apologize for any inconvenience this issue may have caused.
To investigate further, we will need a troubleshoot file from your device downloaded after the issue occurs. I have sent you a form to fill out—once completed, I will contact you privately so that you can share the troubleshoot file.
I also have this problem, but with an RUTX11 with failover configured across mobile and multiwan interfaces and a wireguard VPN connection to my home. Failover is working, and the wireguard connection is established, but traffic isn’t being routed over wireguard as it should be. This worked fine before updating to RUTX_R_00.07.15.2.
I’d rather avoid having to downgrade and reconfigure everything manually if possible…
Could you please share a screenshot of the WireGuard peer configuration window from the WebUI? Kindly make sure to blur or hide any sensitive information before sending it.
By the way, I tried removing the Multi AP settings and re-adding the main client settings individually (so in Network > Wireless > SSIDs I now have one Mode: Client instead of one Mode: Multi AP with several clients configured within it), but that made no difference.
One oddity, which might be a clue, is that under Network > Failover > Multiwan, in the Interface tab, if I edit Name:wwan (the name I gave the Network for the wireless client), in the top section it says:
I’m currently on vacation and have not much time to diagnose - also I cannot now revert firmware and reconfigure as I need the service while travelling abroad.
@Marija can you please update this thread once RnD have further diagnosed the bug? thanks
It’s resolved for me by a test firmware that tech support sent me, although at first it did not work because I’d changed something while attempting to work around the problem, but tech support diagnosed what I’d done and helped me to resolve that. Now the failover is working again for me (wifi client is now chosen as the preferred WAN when available, and otherwise it fails over to mobile data, and also I don’t need to add manual routes for the Wireguard VPN to work).
