Teltonika router guide

RUTX50 Ping Reboot Guide

Ping reboot on the Teltonika RUTX50 5G router: dual-SIM hosts, ping from mobile, and why 5G routers need a little more patience.

ModelRUTX50 Category5G Network5G LevelIntermediate

The RUTX50 is the router I most often see on sites that wanted 5G throughput: video, temporary offices, fixed wireless access. A 5G modem takes longer to come back after a restart than a basic 4G one, and some sites move between 5G and 4G during the day. Both of those affect how aggressive you can safely make ping reboot.

RUTX50 ping reboot at a glance

RouterTeltonika RUTX50, industrial 5G router
Ports5 x Gigabit Ethernet, WiFi, GPS
SIMDual SIM
WhereSystem, Maintenance, Auto Reboot, Ping/Wget Reboot
First actionRestart mobile connection
Biggest trapActing too quickly while the 5G modem is still reattaching

Teltonika lists the RUTX50 as end of life. There are a lot of them still in service, which is why this guide exists, but for new installs check Teltonika’s current range. The ping reboot settings below carry straight over to current RutOS models.

What is different about 5G

Two things. First, recovery takes longer. After a modem restart or a full reboot, a 5G router needs more time to reattach and bring the data session back than a small 4G router does, so a rule that checks again too soon can decide the link has failed while it is still coming up. Keep at least a few minutes between checks.

Second, 5G coverage at the edge of a cell can come and go, with the modem dropping back to 4G. Brief interruptions during those changes are normal. Three failures at a 5-minute interval rides through them. One failure at a 1-minute interval does not.

Configuring ping reboot on the RUTX50

Everything below is on current RutOS 7 firmware. The menu names come from Teltonika’s own RUTX50 documentation. Older firmware put the same feature under Services, Auto Reboot, and called some fields by different names, so update the firmware first if what you see does not match.

  1. Test the target by hand. Before you touch the rule, ping the address you plan to use from the router’s diagnostics page. If it does not answer there, it will not answer for ping reboot either.
  2. Open the rule. Go to System, Maintenance, Auto Reboot. The Ping/Wget Reboot section has one rule already filled in, switched off. Click the pencil icon to edit it.
  3. Choose the check. Set Type to Ping. On this model RutOS also offers a TCP connection check, which helps where ICMP is filtered.
  4. Choose the action. Set Action if no echo is received to Restart mobile connection. It drops and re-establishes the data session without taking the whole router down. Modem reboot and Device reboot are heavier options for a second rule.
  5. Set the timing. Interval 5 minutes, Timeout 5 seconds, Interval count 2. Interval count is the number of extra attempts after the first one, so 2 means the router acts after three consecutive failures, about 15 minutes of failed checks.
  6. Set the hosts. For an internet SIM, use two addresses from different operators, such as 8.8.8.8 and 9.9.9.9, and set Action condition to When all requests fail. On a closed private APN, use an address inside the APN instead.
  7. Save and test. Save and apply, then prove it works: point the rule at an address you know will not answer, wait for the action, check the event log, and put the real target back.

The RUTX50 has two SIM slots, so the rule shows a host field for each SIM: Host to ping from SIM 1 and Host to ping from SIM 2. Set both. If the two SIMs are on different network types, for example one internet SIM and one private APN SIM, each needs a target that SIM can actually reach. The router only acts when all the hosts defined for the active SIM fail to reply.

Interface matters on the RUTX50, because it can take a wired WAN as well as mobile. Left on Automatically selected, the pings go out through whichever interface is currently the main WAN. If the fixed line is primary, you are testing the fixed line, not the 4G or 5G backup. Set Ping from mobile when the rule is there to protect the mobile connection.

The settings I start with

TypePing
Action if no echo is receivedRestart mobile connection
Interval5 minutes
Timeout5 seconds
Interval count2 (three failures in total)
Action conditionWhen all requests fail
Host to ping8.8.8.8 and 9.9.9.9 on an internet SIM, an address inside the APN on a private one
InterfacePing from mobile

Then add a second rule with a longer interval, 30 minutes for example, and the action set to Device reboot. If restarting the mobile connection has not cleared the fault, the heavier action gets a turn. The settings builder works these values out for your SIM type, and the recovery and reboot loop calculator shows how long a stalled link stays down with them.

Two settings people miss

No action on data limit. If you use RutOS mobile data limits, switch this on. Without it, a SIM that has hit its cap fails every ping, and the router restarts the connection over and over while nothing can possibly get through.

Send SMS. The action list includes Send SMS instead of a restart. On a site where an unexpected restart would do damage, an SMS alert is a sensible first rule, with the restart as a second rule further out.

Troubleshooting

It reboots every few minutes

Nearly always the target. A public address on a private APN can never answer, so every check fails and the router cycles. I explain why in the ping reboot cycle of death and what to use instead in Ping Reboot on Private IP SIM Cards.

Check the rule is switched on, that the host is set for the SIM that is actually active, and that Interface is pinging the path you think it is. On a dual-WAN site, a healthy fixed line will keep answering the pings while the mobile backup is dead.

Then a restart is not the fix. A barred SIM, a data cap, wrong APN settings or a roaming SIM stuck on a network that will not pass data all look like a dead link, and none of them are cured by rebooting. See roaming SIMs that get stuck.

For the other recovery features in RutOS, such as the reboot scheduler, SMS reboot and the hardware watchdog, see Teltonika Router Auto-Reboot and Resilience Features.

Questions

Where is ping reboot on the RUTX50?

On RutOS 7 it is under System, Maintenance, Auto Reboot, in the Ping/Wget Reboot section. There is one rule already filled in with 8.8.8.8, switched off by default.

What does Interval count mean on the RUTX50?

It is the number of extra attempts after the first failed one. With Interval count 2, the router acts after three consecutive failures.

Should the RUTX50 restart the connection or reboot?

Restart mobile connection first. It is quicker and keeps the router up. Add a second rule with a longer interval that does a full Device reboot if the restart did not fix it.

Do I need separate ping hosts for each SIM on the RUTX50?

Yes, set Host to ping from SIM 1 and from SIM 2. Each must be reachable from that SIM, which matters if one SIM is on a private APN.