I am using a Teltonika RUTX50 router and I would like to implement a WAN failover mechanism based on downlink throughput, rather than traditional connectivity checks (ping or wget).
My requirements are:
• Primary WAN: Mobile (SIM card 1)
• Backup WAN 1 (Optional): Mobile (SIM card 2)
• Backup WAN 2: Fixed Ethernet WAN
Failover condition:
When the downlink throughput of the mobile WAN drops below a defined threshold (e.g., 15 Mbps) and remains there for a short period (e.g., 30 seconds), the router should automatically:
1. Stop using SIM 1 / mobile WAN for data transmission.
2. Switch to SIM 2 / mobile WAN (if SIM 2 is installed).
3. If SIM 2 also drops below the throughput threshold, switch to the fixed Ethernet WAN as the active WAN interface.
Additionally, when the mobile WAN throughput recovers above the threshold, the router may switch back to the mobile WAN.
I am aware that RutOS offers failover based on:
• Ping / ICMP checks
• HTTP / wget type connectivity tests
However, these methods primarily verify reachability and do not reflect the actual usable throughput of the mobile link.
My questions are:
1. Is there any built-in feature in the current RUTX50 / RutOS firmware that allows failover based directly on measured throughput (download speed), rather than just ping or HTTP reachability?
2. If not, what is the recommended and officially supported approach for implementing such behavior?
For example, is it acceptable and supported to use custom scripts and cron jobs on the RUTX50 that:
• Periodically perform a small download or speed test on the mobile WAN,
• Evaluate the resulting throughput, and
• Use ifup/ifdown or other RutOS APIs/commands to change the active WAN?
3. Are there any official examples, documentation, or best practices from Teltonika regarding:
• Measuring WAN throughput on RUTX devices, and
• Safely triggering failover between mobile WAN and Ethernet WAN based on those measurements?
Device details:
• Model: RUTX50
• Firmware version: RUTX_R_00.07.19.4
• Internal modem firmware version: RG501QEUAAR12A11M4G
• Kernel version 6.6.108
Any guidance, recommended configuration, example scripts, or the possibility of a tailored firmware solution from your side would be greatly appreciated, as this capability is important for ensuring stable service on my network.
Thank you in advance for your support.