Ping reboot proves one thing: that an ICMP echo request can reach a target and come back. Most of the time that is a good stand-in for a working connection. Sometimes it is not, and the router reports healthy while nothing actually works. That is where a wget check earns its place.
Ping vs wget at a glance
| Ping reboot | Sends ICMP echo requests. Tests that a path exists. Tiny, quick, works anywhere ICMP is allowed. |
| Wget reboot | Fetches a web address. Tests DNS, a TCP connection and an HTTP reply. |
| Use ping for | The frequent, lightweight check |
| Use wget for | A slower second check that the service really works |
| Wget needs | A URL the router can reach, so on a closed APN it needs a web server inside the APN |
How ping passes while the service is dead
- DNS has failed. The router can ping an IP address but cannot resolve names, so every application that uses a hostname fails.
- ICMP gets through but TCP does not. A firewall, proxy or operator network treats ping differently from real traffic.
- The far end is half alive. A server answers ping while the application on it has stopped.
- The data path is degraded. Small ping packets get through, larger application traffic does not.
What wget tests
A wget check asks the router to fetch a web address. To succeed it has to resolve the name, open a TCP connection, and get an HTTP response back. If any of those fail, the check fails. Teltonika RutOS offers it as a type in the same Ping/Wget Reboot rule, with the same actions and timing.
How I use them together
Ping every 5 minutes as the main check, with restart mobile connection as the action. Wget every 30 to 60 minutes as a second rule, fetching a small page, with a full reboot as the action. If the quick check passes but the deep one fails, something more than a stalled session is wrong.
Point wget at a small page you control if you can. A large public home page wastes data on a metered SIM, and you have no say in when it changes or moves.
If ping is passing but a VPN is the thing that has failed, the answer is a different target rather than a different method: see ping reboot over a VPN.
Questions
What is wget reboot?
A connection check that fetches a web address instead of sending a ping. It tests DNS, a TCP connection and an HTTP reply, and acts if any of them fail.
Should I use wget instead of ping?
Use both. Ping is the quick, frequent check. Wget is a slower second check that catches cases where ping passes but applications fail.