Teltonika router guide

RUT241 Ping Reboot Guide

How to set up ping reboot on the Teltonika RUT241: the RutOS menu path, the settings I use, and the mistakes that cause reboot loops.

ModelRUT241 Category4G Network4G, CAT4 LTE LevelBeginner

The RUT241 is the router I see most often in small remote cabinets: CCTV, metering, a sensor gateway on a single 4G SIM. It is small, it is cheap enough to fit everywhere, and because it runs the same RutOS as Teltonika’s bigger routers, it has the same ping reboot feature. This is how I set it up.

RUT241 ping reboot at a glance

RouterTeltonika RUT241, compact industrial 4G (LTE) router
Ports2 x Ethernet, WiFi
SIMSingle SIM
WhereSystem, Maintenance, Auto Reboot, Ping/Wget Reboot
First actionRestart mobile connection
Biggest trapLeaving 8.8.8.8 as the host on a private APN SIM

Why the RUT241 needs ping reboot

A single-SIM router in a cabinet has exactly one way to reach the outside world. If its mobile data session stalls, and the modem still reports that it is registered with signal, nothing else on the site will notice or fix it. Ping reboot is the part of the router that notices. On a RUT241 it is the most important setting after the APN.

Configuring ping reboot on the RUT241

Everything below is on current RutOS 7 firmware. The menu names come from Teltonika’s own RUT241 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.
  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 RUT241 has a single SIM slot, so there is one set of hosts to configure. That keeps it simple, but it also means there is no second SIM to fall back to: if the SIM is barred or out of credit, no ping reboot setting will fix it.

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
InterfaceAutomatically selected

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 RUT241?

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 RUT241?

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 RUT241 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.