Hi @Yaros_lav 

Thanks for bringing this to our attention.

Regarding the issue you have, please understand the fact first. Online detection is the only determinant of whether the router should switch to a backup WAN or not. i.e. If your WAN can still ping the 8.8.8.8, then you are not going to be switched to the backup WAN.

So, what you should troubleshoot is whether your WAN is literally offline. If it is still available and can ping the 8.8.8.8, and the router still gets replies from Google, then it won't switch. If it is just congestion, but ping still works, then it stays on (primary) WAN. There's nothing we can do to fix it.

(Switching to the backup WAN may take a few seconds or up to a minute. The preset time cannot be changed at this moment.)

About the "jumping IP addresses", that's how the load balancing works. You did not include the WAN/LAN 2 into the secondary (backup) WAN, then it is in active use and the router will balance the traffic between the primary and this WAN/LAN 2, of course.

If you don't want this and want to fix this, you can use policy routing to specify the traffic where it is supposed to flow. Destine your RDP connection to one of the WANs.

(BTW, are you sure RDP is disconnecting because of load balancing? As the RDP is using TCP and should not be disconnected if your session is made)