Occasional drops, router unfortunately stays offline until reboot, doesn't seem to retry

General discussion
1

I find with Turris that at times, probably when some error occurs, even though service is restored by the attached cable modem, Internet (at least DNS) access goes down and remains down until I reboot.

As follows:

dcampbel@LATITUDE ~
$ ssh root@192.168.16.1
root@192.168.16.1's password:


BusyBox v1.29.3 () built-in shell (ash)

  _______  _    _  _____   _____   _____   _____
 |__   __|| |  | ||  __ \ |  __ \ |_   _| / ____|
    | |   | |  | || |__) || |__) |  | |  | (___
    | |   | |  | ||  _  / |  _  /   | |   \___ \
    | |   | |__| || | \ \ | | \ \  _| |_  ____) |
    |_|    \____/ |_|  \_\|_|  \_\|_____||_____/



root@turris:~# ping www.google.com
ping: unknown host www.google.com
root@turris:~# reboot
root@turris:~# Connection to 192.168.16.1 closed by remote host.
Connection to 192.168.16.1 closed.

dcampbel@LATITUDE ~
$ ping www.google.com
PING www.google.com (216.58.196.132): 56 data bytes
64 bytes from 216.58.196.132: icmp_seq=0 ttl=55 time=32 ms
64 bytes from 216.58.196.132: icmp_seq=1 ttl=55 time=22 ms

----www.google.com PING Statistics----
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip (ms)  min/avg/max/med = 22/27/32/27

dcampbel@LATITUDE ~
2

This seems like TOS version 3.x?

There might be link sensing issues between the the upstream cable modem and the TO in cases where the upstream modem has its upstream connectivity (with ISP) interrupted/restored.

If you observe such loss of connectivity you could check on the TO cli

  • ifstatus wan (not sure whether command is available in TOS3.x), or
  • ubus call network.interface.wan status (not sure whether command is available in TOS3.x), or
  • ip l and look for the link status of the TO’s interface that connects to the modem

if the link status is up then you could check connectivity from cli with check_connection

There other forum threads reporting similar symptoms.