Weird Problem (WAN disconnect every saturday or sunday)

Installing and Using OpenWrt
21

The DHCP client performed a scheduled DHCP renew and obtained the same IP address and mask.
Perhaps you should use another method to detect the issue inside the script.

22 
Thu Dec 24 00:22:20 2020 daemon.notice netifd: wan (1843): udhcpc: sending renew to 10.88.128.1
Thu Dec 24 00:22:20 2020 daemon.notice netifd: wan (1843): udhcpc: lease of 10.88.131.10 obtained, lease time 3600
Thu Dec 24 00:22:20 2020 user.notice /etc/udhcpc.user: /lib/netifd/dhcp.script /tmp/udhcpc.user.log renew
Thu Dec 24 00:22:20 2020 user.notice /etc/udhcpc.user: /lib/netifd/dhcp.script 10.88.131.10/19/10.88.159.255 lease:3600
Thu Dec 24 00:22:20 2020 user.notice /etc/udhcpc.user: INTERFACE: wan interface: eth1
Thu Dec 24 00:22:20 2020 user.notice udhcpc: renew 10.88.131.10/19
Thu Dec 24 00:52:20 2020 daemon.notice netifd: wan (1843): udhcpc: sending renew to 10.88.128.1
Thu Dec 24 01:07:20 2020 daemon.notice netifd: wan (1843): udhcpc: sending renew to 10.88.128.1
Thu Dec 24 01:14:50 2020 daemon.notice netifd: wan (1843): udhcpc: sending renew to 10.88.128.1
Thu Dec 24 01:18:35 2020 daemon.notice netifd: wan (1843): udhcpc: sending renew to 10.88.128.1
Thu Dec 24 01:20:27 2020 daemon.notice netifd: wan (1843): udhcpc: sending renew to 10.88.128.1
Thu Dec 24 01:21:23 2020 daemon.notice netifd: wan (1843): udhcpc: sending renew to 0.0.0.0
Thu Dec 24 01:21:26 2020 daemon.notice netifd: wan (1843): udhcpc: lease of 10.88.131.10 obtained, lease time 3600
Thu Dec 24 01:21:26 2020 user.notice /etc/udhcpc.user: /lib/netifd/dhcp.script /tmp/udhcpc.user.log renew
Thu Dec 24 01:21:26 2020 user.notice /etc/udhcpc.user: /lib/netifd/dhcp.script 10.88.131.10/19/10.88.159.255 lease:3600
Thu Dec 24 01:21:26 2020 user.notice /etc/udhcpc.user: INTERFACE: wan interface: eth1
Thu Dec 24 01:21:26 2020 user.notice udhcpc: renew 10.88.131.10/19

this is weird, I let the router be without restarting wan interfaces and the next morning when I checked I see the internet already back, about 1 hours since last request renew failed.

23

You can try using this app:

2 Likes
24

sorry for late reply, I've already used pingcheck that trigger restart wan interface after failed ping, although not quite ideal in my personal opinion (having to ping every x minutes). Is watchcat similar like these? seems it have advantages of having GUI interfaces than pingcheck.

1 Like