subscribe to our Youtube


14455 questions

17168 answers


0 members

We are migrating to our new platform at Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
488 views 1 comments
by anonymous

We have a computer that is connected to a RUT241 via WiFi. We periodically check (every 5 minutes) if the connection to the router is working (by sending a ping to the router). This works great on many of our setups where we use the RUT240. We recently tested the RUT241 and it quite often doesn't respond to the ping (once an hour at least). What's weird is, that when the ping command returns with "Destination Host Unreachable", the response is coming from an IP address that we do not recognize ( Even though the command "ip route show default" says that it's connected via wifi and the default route to the router is Any ideas what could cause such issues?

64 bytes from icmp_seq=1 ttl=64 time=1.94 ms
default via dev wlan0 proto dhcp src metric 302
From icmp_seq=1 Destination Host Unreachable
default via dev wlan0 proto dhcp src metric 302
64 bytes from icmp_seq=1 ttl=64 time=2.04 ms
default via dev wlan0 proto dhcp src metric 302

1 Answer

0 votes
by anonymous


I would like you to attach a troubleshoot file from RUT241 to your question. Please, replicate the issue, then access router's WebUI, go to System -> Administration -> Troubleshoot section and download troubleshoot file from there. Make sure the device has been up for a longer period of time. The logs in the file might provide more insight into the issue.

Attached files are private and visible only to Teltonika Moderators.

Best regards

by anonymous
Thank you for the response. I've kept the router running for 2 weeks now and the issue hasn't occurred again.

I found out that the router had blocked the device due to some invalid login attempts (trying to send SMS via the SMS gateway) however after unblocking it (WebUI -> System -> Administrator -> Access Control -> Security -> Login Attempts) (and waiting for ~24hours) all ping requests were answered properly.