Hi, i have a tplink er605 with 23.05 installed. On the wan port there is an outdoor cpe modem configured in ip passtrough mode.
All is working good, except sometimes i cannot get internet access for few seconds. It happens with wifi and eth clients. Modem is not reconnecting when it happens.
So, i would check if problem could be er605 with openwrt. Can you help me to understand it? What i should check when it happens?
Checking luci logs and it seems all goods.
Sounds like a problem with the upstream device, not your openwrt router.
That said, we can look at logs…
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
ubus call system board
cat /etc/config/network
logread -e udhcpc
Hi, here the infos.
ubus call system board
{
"kernel": "5.15.134",
"hostname": "OpenWrt",
"system": "MediaTek MT7621 ver:1 eco:3",
"model": "TP-Link ER605 v2",
"board_name": "tplink,er605-v2",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "23.05.0",
"revision": "r23497-6637af95aa",
"target": "ramips/mt7621",
"description": "OpenWrt 23.05.0 r23497-6637af95aa"
}
}
cat /etc/config/network
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd32:12d1:8090::/48'
option packet_steering '1'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth1'
list ports 'eth2'
list ports 'eth3'
list ports 'eth4'
config device
option name 'eth1'
option macaddr '24:2F:D0:6D:EA:F0'
config device
option name 'eth2'
option macaddr '24:2F:D0:6D:EA:F0'
config device
option name 'eth3'
option macaddr '24:2F:D0:6D:EA:F0'
config device
option name 'eth4'
option macaddr '24:2F:D0:6D:EA:F0'
config interface 'lan'
option device 'br-lan.10'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
config device
option name 'eth0'
option macaddr '24:2F:D0:6d:ea:f1'
config interface 'wan'
option device 'eth0'
option proto 'dhcp'
option peerdns '0'
list dns '8.8.8.8'
list dns '8.8.4.4'
config interface 'wan6'
option device 'eth0'
option proto 'dhcpv6'
option reqaddress 'try'
option reqprefix 'auto'
option peerdns '0'
config bridge-vlan
option device 'br-lan'
option vlan '10'
list ports 'eth1:u*'
list ports 'eth4:t*'
config bridge-vlan
option device 'br-lan'
option vlan '20'
list ports 'eth4:t'
config bridge-vlan
option device 'br-lan'
option vlan '30'
list ports 'eth4:t'
config bridge-vlan
option device 'br-lan'
option vlan '40'
list ports 'eth4:t'
config interface 'SECURITY'
option proto 'static'
option device 'br-lan.20'
option ipaddr '192.168.2.1'
option netmask '255.255.255.0'
config interface 'HOME'
option proto 'static'
option device 'br-lan.30'
option ipaddr '192.168.3.1'
option netmask '255.255.255.0'
config interface 'GUEST'
option proto 'static'
option device 'br-lan.40'
option ipaddr '192.168.4.1'
option netmask '255.255.255.0'
logread -e udhcpc (after reboot)
Tue Jul 8 03:25:35 2025 daemon.notice netifd: wan (2327): udhcpc: started, v1.36.1
Tue Jul 8 03:25:36 2025 daemon.notice netifd: wan (2327): udhcpc: broadcasting discover
Tue Jul 8 03:25:39 2025 daemon.notice netifd: wan (2327): udhcpc: broadcasting discover
Tue Jul 8 03:25:39 2025 daemon.notice netifd: wan (2327): udhcpc: broadcasting select for 151.XX.X.188, server 151.XX.X.189
Tue Jul 8 03:25:39 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 16:36:14 2025 daemon.notice netifd: wan (2327): udhcpc: sending renew to server 151.XX.X.189
Sat Jul 12 16:36:14 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 16:41:14 2025 daemon.notice netifd: wan (2327): udhcpc: sending renew to server 151.XX.X.189
Sat Jul 12 16:41:14 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 16:46:14 2025 daemon.notice netifd: wan (2327): udhcpc: sending renew to server 151.XX.X.189
Sat Jul 12 16:46:14 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 16:51:15 2025 daemon.notice netifd: wan (2327): udhcpc: sending renew to server 151.XX.X.189
Sat Jul 12 16:51:15 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 16:56:15 2025 daemon.notice netifd: wan (2327): udhcpc: sending renew to server 151.XX.X.189
Sat Jul 12 16:56:15 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 17:01:15 2025 daemon.notice netifd: wan (2327): udhcpc: sending renew to server 151.XX.X.189
Sat Jul 12 17:01:15 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 17:06:15 2025 daemon.notice netifd: wan (2327): udhcpc: sending renew to server 151.XX.X.189
Sat Jul 12 17:06:15 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 17:11:15 2025 daemon.notice netifd: wan (2327): udhcpc: sending renew to server 151.XX.X.189
Sat Jul 12 17:11:15 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 17:16:16 2025 daemon.notice netifd: wan (2327): udhcpc: sending renew to server 151.XX.X.189
Sat Jul 12 17:16:16 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 17:21:16 2025 daemon.notice netifd: wan (2327): udhcpc: sending renew to server 151.XX.X.189
Sat Jul 12 17:21:16 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 17:26:16 2025 daemon.notice netifd: wan (2327): udhcpc: sending renew to server 151.XX.X.189
Sat Jul 12 17:26:16 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 17:31:16 2025 daemon.notice netifd: wan (2327): udhcpc: sending renew to server 151.XX.X.189
Sat Jul 12 17:31:16 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 17:36:15 2025 daemon.notice netifd: wan (2327): udhcpc: sending renew to server 151.XX.X.189
Sat Jul 12 17:36:15 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 17:41:15 2025 daemon.notice netifd: wan (2327): udhcpc: sending renew to server 151.XX.X.189
Sat Jul 12 17:41:15 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 17:46:16 2025 daemon.notice netifd: wan (2327): udhcpc: sending renew to server 151.XX.X.189
Sat Jul 12 17:46:16 2025 daemon.notice netifd: wan (2327): udhcpc: lease of 151.XX.X.188 obtained from 151.XX.X.189, lease time 600
Sat Jul 12 17:48:52 2025 daemon.notice netifd: wan (2327): udhcpc: received SIGTERM
Sat Jul 12 17:48:52 2025 daemon.notice netifd: wan (2327): udhcpc: unicasting a release of 151.XX.X.188 to 151.XX.X.189
Sat Jul 12 17:48:52 2025 daemon.notice netifd: wan (2327): udhcpc: sending release
Sat Jul 12 17:48:52 2025 daemon.notice netifd: wan (2327): udhcpc: entering released state
Sat Jul 12 17:48:54 2025 daemon.notice netifd: wan (8977): udhcpc: started, v1.36.1
Sat Jul 12 17:48:54 2025 daemon.notice netifd: wan (8977): udhcpc: broadcasting discover
Sat Jul 12 17:48:56 2025 daemon.notice netifd: wan (8977): udhcpc: received SIGTERM
Sat Jul 12 17:48:56 2025 daemon.notice netifd: wan (8977): udhcpc: entering released state
Sat Jul 12 17:49:00 2025 daemon.notice netifd: wan (9192): udhcpc: started, v1.36.1
Sat Jul 12 17:49:00 2025 daemon.notice netifd: wan (9192): udhcpc: broadcasting discover
Sat Jul 12 17:49:03 2025 daemon.notice netifd: wan (9192): udhcpc: broadcasting discover
Sat Jul 12 17:49:04 2025 daemon.notice netifd: wan (9192): udhcpc: received SIGTERM
Sat Jul 12 17:49:04 2025 daemon.notice netifd: wan (9192): udhcpc: entering released state
Sat Jul 12 17:49:06 2025 daemon.notice netifd: wan (9409): udhcpc: started, v1.36.1
Sat Jul 12 17:49:06 2025 daemon.notice netifd: wan (9409): udhcpc: broadcasting discover
Sat Jul 12 17:49:08 2025 daemon.notice netifd: wan (9409): udhcpc: received SIGTERM
Sat Jul 12 17:49:08 2025 daemon.notice netifd: wan (9409): udhcpc: entering released state
Sat Jul 12 17:49:10 2025 daemon.notice netifd: wan (9624): udhcpc: started, v1.36.1
Sat Jul 12 17:49:10 2025 daemon.notice netifd: wan (9624): udhcpc: broadcasting discover
Sat Jul 12 17:49:13 2025 daemon.notice netifd: wan (9624): udhcpc: broadcasting discover
Sat Jul 12 17:49:13 2025 daemon.notice netifd: wan (9624): udhcpc: broadcasting select for 151.XX.X.249, server 151.XX.X.250
Sat Jul 12 17:49:13 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 17:54:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 17:54:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 17:59:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 17:59:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 18:04:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 18:04:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 18:09:13 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 18:09:13 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 18:14:13 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 18:14:13 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 18:19:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 18:19:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 18:24:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 18:24:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 18:29:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 18:29:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 18:34:13 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 18:34:13 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 18:39:13 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 18:39:13 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 18:44:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 18:44:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 18:49:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 18:49:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 18:54:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 18:54:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 18:59:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 18:59:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 19:04:13 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 19:04:13 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 19:09:13 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 19:09:13 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 19:14:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 19:14:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 19:19:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 19:19:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 19:24:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 19:24:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 19:29:13 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 19:29:13 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 19:34:13 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 19:34:13 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 19:39:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 19:39:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 19:44:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 19:44:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 19:49:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 19:49:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 19:54:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 19:54:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 19:59:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 19:59:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 20:04:15 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 20:04:15 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 20:09:15 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 20:09:15 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 20:14:15 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 20:14:15 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 20:19:15 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 20:19:15 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 20:24:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 20:24:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 20:29:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 20:29:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 20:34:15 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 20:34:15 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 20:39:15 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 20:39:15 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 20:44:15 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 20:44:15 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 20:49:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 20:49:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 20:54:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 20:54:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 20:59:15 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 20:59:15 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 21:04:15 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 21:04:15 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 21:09:15 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 21:09:15 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 21:14:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 21:14:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 21:19:14 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 21:19:14 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 21:24:15 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 21:24:15 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 21:29:15 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 21:29:15 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 21:34:15 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 21:34:15 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 21:39:15 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 21:39:15 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 21:44:16 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 21:44:16 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 21:49:16 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 21:49:16 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 21:54:16 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 21:54:16 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 21:59:16 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 21:59:16 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 22:04:16 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 22:04:16 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 22:09:17 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 22:09:17 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 22:14:17 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 22:14:17 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 22:19:17 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 22:19:17 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 22:24:17 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 22:24:17 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 22:29:17 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 22:29:17 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 22:34:18 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 22:34:18 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 22:39:18 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 22:39:18 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 22:44:18 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 22:44:18 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 22:49:18 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 22:49:18 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 22:54:17 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 22:54:17 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 22:59:17 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 22:59:17 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 23:04:18 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 23:04:18 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 23:09:18 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 23:09:18 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 23:14:18 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 23:14:18 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 23:19:18 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 23:19:18 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 23:24:18 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 23:24:19 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 23:29:19 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 23:29:19 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 23:34:19 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 23:34:19 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 23:39:19 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 23:39:19 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 23:44:19 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 23:44:19 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 23:49:19 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 23:49:19 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 23:54:20 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 23:54:20 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sat Jul 12 23:59:20 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sat Jul 12 23:59:20 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sun Jul 13 00:04:20 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sun Jul 13 00:04:20 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
Sun Jul 13 00:09:20 2025 daemon.notice netifd: wan (9624): udhcpc: sending renew to server 151.XX.X.250
Sun Jul 13 00:09:20 2025 daemon.notice netifd: wan (9624): udhcpc: lease of 151.XX.X.249 obtained from 151.XX.X.250, lease time 600
I didn't encounter the problem today, as I wasn't at home. I'll check the command immediately when it occurs.
It looks like you had an outage here:
your ISP gives you a leasetime of just 10 minutes, but the SIGTERM occurred must sooner than that -- only ~2.5 mins after the lease was issued -- indicating that it is not a DHCP lease issue.
If this hasn't flushed out of the system, let's see what is happening between 17:46 and 17:48:52.
The IP address changed so the old one was released. An address change would at the least break the NAT associations in the upstream network.
Yeah. Bit the fact that there is a sigterm for dhcp only 2.5 mins after the lease is acquired (rather than at the lease expiration time) is what I find unusual.
Maybe a bad cable and/or an issue with the upstream link/hardware?? I would like to know what caused the sigterm.
The device connected to wan port is a zte cpe 4g/5g. From it i can change via web interface the release time for dhcp. Anyway, as you can see from log, cpe release the same ip and do/should do it for 24.hours.After 24h, my isp force a new ip release.
But, that sigterm in the log is not due to 24h isp rule, and i don't know why it happened.
EDIT: this night i changed lease time of CPE to 120000 seconds. In the log i read:
Sun Jul 13 02:41:02 2025 daemon.notice netifd: wan (14928): udhcpc: broadcasting select for 151.XX.X.50, server 151.XX.X.49
Sun Jul 13 02:41:03 2025 daemon.notice netifd: wan (14928): udhcpc: lease of 151.XX.X.50 obtained from 151.XX.X.49, lease time 120000
Sun Jul 13 19:21:03 2025 daemon.notice netifd: wan (14928): udhcpc: sending renew to server 151.XX.X.49
Sun Jul 13 19:21:03 2025 daemon.notice netifd: wan (14928): udhcpc: lease of 151.XX.X.50 obtained from 151.XX.X.49, lease time 120000
Why renew request happened before 120000 seconds?
So releasing same IP each 600 seconds does not break NAT associations?
It would not because the same IP stays in the NAT tables. If the client gets a different IP all connections are broken until new NAT entries are established.
The renew request will happen at 1/2 the lease time. If that is not successful, it will try again at 87.5% of the lease duration, and then again at the expiry of the lease.
If the renew is happening before 1/2 the lease time, that means that something else is causing the interface to glitch... for example, a bad cable or other interruption.
Next time you have an outage, look for the DHCP SIGTERM and then grab the logs in the immediate vicinity.
Ok. Which log should i check exactly?
The standard log. You can see the output with the logread command. If you do logread -e udhcpc you'll see all the DHCP client related events. Once you find a SIGTERM from that process make a note of the timestamp and then run logread again to look for other events that occurred around the same time.
SIGTERM
Mon Jul 14 16:02:00 2025 daemon.notice netifd: wan (8538): udhcpc: received SIGTERM
Mon Jul 14 16:02:00 2025 daemon.notice netifd: wan (8538): udhcpc: unicasting a release of 151.XX.X.83 to 151.XX.X.84
Mon Jul 14 16:02:00 2025 daemon.notice netifd: wan (8538): udhcpc: sending release
Mon Jul 14 16:02:00 2025 daemon.notice netifd: wan (8538): udhcpc: entering released state
Mon Jul 14 16:02:02 2025 daemon.notice netifd: wan (3792): udhcpc: started, v1.36.1
Mon Jul 14 16:02:02 2025 daemon.notice netifd: wan (3792): udhcpc: broadcasting discover
Mon Jul 14 16:02:04 2025 daemon.notice netifd: wan (3792): udhcpc: received SIGTERM
Mon Jul 14 16:02:04 2025 daemon.notice netifd: wan (3792): udhcpc: entering released state
Mon Jul 14 16:02:07 2025 daemon.notice netifd: wan (4105): udhcpc: started, v1.36.1
Mon Jul 14 16:02:07 2025 daemon.notice netifd: wan (4105): udhcpc: broadcasting discover
Mon Jul 14 16:02:10 2025 daemon.notice netifd: wan (4105): udhcpc: broadcasting discover
Mon Jul 14 16:02:10 2025 daemon.notice netifd: wan (4105): udhcpc: received SIGTERM
Mon Jul 14 16:02:10 2025 daemon.notice netifd: wan (4105): udhcpc: entering released state
Mon Jul 14 16:02:12 2025 daemon.notice netifd: wan (4295): udhcpc: started, v1.36.1
Mon Jul 14 16:02:12 2025 daemon.notice netifd: wan (4295): udhcpc: broadcasting discover
Mon Jul 14 16:02:14 2025 daemon.notice netifd: wan (4295): udhcpc: received SIGTERM
Mon Jul 14 16:02:14 2025 daemon.notice netifd: wan (4295): udhcpc: entering released state
Mon Jul 14 16:02:17 2025 daemon.notice netifd: wan (4536): udhcpc: started, v1.36.1
Mon Jul 14 16:02:18 2025 daemon.notice netifd: wan (4536): udhcpc: broadcasting discover
Mon Jul 14 16:02:21 2025 daemon.notice netifd: wan (4536): udhcpc: broadcasting discover
Mon Jul 14 16:02:21 2025 daemon.notice netifd: wan (4536): udhcpc: broadcasting select for 151.XX.X.251, server 151.XX.X.252
Mon Jul 14 16:02:21 2025 daemon.notice netifd: wan (4536): udhcpc: lease of 151.XX.X.251 obtained from 151.XX.X.252, lease time 120000
LOG
Mon Jul 14 15:53:56 2025 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan.30) XX:XX:XX:XX:XX:XX
Mon Jul 14 15:53:56 2025 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan.30) 192.168.3.229 XX:XX:XX:XX:XX:XX
Mon Jul 14 15:53:56 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.30) 192.168.3.229 XX:XX:XX:XX:XX:XX
Mon Jul 14 15:53:56 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.30) 192.168.3.229 XX:XX:XX:XX:XX:XX
Mon Jul 14 15:56:30 2025 daemon.warn odhcpd[1436]: No default route present, overriding ra_lifetime!
Mon Jul 14 15:56:40 2025 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan.30) XX:XX:XX:XX:XX:XX
Mon Jul 14 15:56:40 2025 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan.30) 192.168.3.229 XX:XX:XX:XX:XX:XX
Mon Jul 14 15:56:40 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.30) 192.168.3.229 XX:XX:XX:XX:XX:XX
Mon Jul 14 15:56:40 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.30) 192.168.3.229 XX:XX:XX:XX:XX:XX
Mon Jul 14 15:58:46 2025 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan.30) XX:XX:XX:XX:XX:XX
Mon Jul 14 15:58:46 2025 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan.30) 192.168.3.229 XX:XX:XX:XX:XX:XX
Mon Jul 14 15:58:46 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.30) 192.168.3.229 XX:XX:XX:XX:XX:XX
Mon Jul 14 15:58:46 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.30) 192.168.3.229 XX:XX:XX:XX:XX:XX
Mon Jul 14 16:01:56 2025 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Mon Jul 14 16:01:56 2025 daemon.info dnsmasq[1]: using nameserver 8.8.8.8#53
Mon Jul 14 16:01:56 2025 daemon.info dnsmasq[1]: using nameserver 8.8.4.4#53
Mon Jul 14 16:01:56 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test
Mon Jul 14 16:01:56 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Mon Jul 14 16:01:56 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Mon Jul 14 16:01:56 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local
Mon Jul 14 16:01:56 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Mon Jul 14 16:01:56 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Mon Jul 14 16:01:56 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Mon Jul 14 16:01:57 2025 daemon.warn odhcpd[1436]: No default route present, overriding ra_lifetime!
Mon Jul 14 16:02:00 2025 kern.info kernel: [171073.969908] mtk_soc_eth 1e100000.ethernet eth0: Link is Down
Mon Jul 14 16:02:00 2025 daemon.notice netifd: Network device 'eth0' link is down
Mon Jul 14 16:02:00 2025 daemon.notice netifd: Interface 'wan' has link connectivity loss
Mon Jul 14 16:02:00 2025 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Mon Jul 14 16:02:00 2025 daemon.notice netifd: wan (8538): udhcpc: received SIGTERM
Mon Jul 14 16:02:00 2025 daemon.notice netifd: wan (8538): udhcpc: unicasting a release of 151.XX.X.83 to 151.XX.X.84
Mon Jul 14 16:02:00 2025 daemon.notice netifd: wan (8538): udhcpc: sending release
Mon Jul 14 16:02:00 2025 daemon.notice netifd: wan (8538): udhcpc: entering released state
Mon Jul 14 16:02:00 2025 daemon.notice netifd: wan (8538): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Mon Jul 14 16:02:00 2025 daemon.notice netifd: Interface 'wan' is now down
Mon Jul 14 16:02:00 2025 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Mon Jul 14 16:02:00 2025 daemon.notice netifd: Interface 'wan6' is now down
Mon Jul 14 16:02:02 2025 kern.info kernel: [171076.050071] mtk_soc_eth 1e100000.ethernet eth0: Link is Up - 100Mbps/Half - flow control off
Mon Jul 14 16:02:02 2025 daemon.notice netifd: Network device 'eth0' link is up
Mon Jul 14 16:02:02 2025 daemon.notice netifd: Interface 'wan' has link connectivity
Mon Jul 14 16:02:02 2025 daemon.notice netifd: Interface 'wan' is setting up now
Mon Jul 14 16:02:02 2025 daemon.notice netifd: Interface 'wan6' has link connectivity
Mon Jul 14 16:02:02 2025 daemon.notice netifd: Interface 'wan6' is setting up now
Mon Jul 14 16:02:02 2025 daemon.notice netifd: wan (3792): udhcpc: started, v1.36.1
Mon Jul 14 16:02:02 2025 daemon.notice netifd: wan (3792): udhcpc: broadcasting discover
Mon Jul 14 16:02:04 2025 kern.info kernel: [171078.129856] mtk_soc_eth 1e100000.ethernet eth0: Link is Down
Mon Jul 14 16:02:04 2025 daemon.notice netifd: Network device 'eth0' link is down
Mon Jul 14 16:02:04 2025 daemon.notice netifd: Interface 'wan' has link connectivity loss
Mon Jul 14 16:02:04 2025 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Mon Jul 14 16:02:04 2025 daemon.notice netifd: wan (3792): udhcpc: received SIGTERM
Mon Jul 14 16:02:04 2025 daemon.notice netifd: wan (3792): udhcpc: entering released state
Mon Jul 14 16:02:04 2025 daemon.notice netifd: wan (3792): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Mon Jul 14 16:02:04 2025 daemon.notice netifd: Interface 'wan' is now down
Mon Jul 14 16:02:04 2025 daemon.notice netifd: Interface 'wan6' is now down
Mon Jul 14 16:02:07 2025 daemon.notice netifd: Network device 'eth0' link is up
Mon Jul 14 16:02:07 2025 daemon.notice netifd: Interface 'wan' has link connectivity
Mon Jul 14 16:02:07 2025 daemon.notice netifd: Interface 'wan' is setting up now
Mon Jul 14 16:02:07 2025 kern.info kernel: [171081.249851] mtk_soc_eth 1e100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Mon Jul 14 16:02:07 2025 daemon.notice netifd: Interface 'wan6' has link connectivity
Mon Jul 14 16:02:07 2025 daemon.notice netifd: Interface 'wan6' is setting up now
Mon Jul 14 16:02:07 2025 daemon.notice netifd: wan (4105): udhcpc: started, v1.36.1
Mon Jul 14 16:02:07 2025 daemon.notice netifd: wan (4105): udhcpc: broadcasting discover
Mon Jul 14 16:02:10 2025 kern.info kernel: [171084.369726] mtk_soc_eth 1e100000.ethernet eth0: Link is Down
Mon Jul 14 16:02:10 2025 daemon.notice netifd: Network device 'eth0' link is down
Mon Jul 14 16:02:10 2025 daemon.notice netifd: Interface 'wan' has link connectivity loss
Mon Jul 14 16:02:10 2025 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Mon Jul 14 16:02:10 2025 daemon.notice netifd: wan (4105): udhcpc: broadcasting discover
Mon Jul 14 16:02:10 2025 daemon.notice netifd: wan (4105): udhcpc: received SIGTERM
Mon Jul 14 16:02:10 2025 daemon.notice netifd: wan (4105): udhcpc: entering released state
Mon Jul 14 16:02:10 2025 daemon.notice netifd: wan (4105): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Mon Jul 14 16:02:10 2025 daemon.notice netifd: Interface 'wan' is now down
Mon Jul 14 16:02:11 2025 daemon.notice netifd: Interface 'wan6' is now down
Mon Jul 14 16:02:12 2025 daemon.notice netifd: Network device 'eth0' link is up
Mon Jul 14 16:02:12 2025 daemon.notice netifd: Interface 'wan' has link connectivity
Mon Jul 14 16:02:12 2025 daemon.notice netifd: Interface 'wan' is setting up now
Mon Jul 14 16:02:12 2025 kern.info kernel: [171086.449872] mtk_soc_eth 1e100000.ethernet eth0: Link is Up - 100Mbps/Half - flow control off
Mon Jul 14 16:02:12 2025 daemon.notice netifd: Interface 'wan6' has link connectivity
Mon Jul 14 16:02:12 2025 daemon.notice netifd: Interface 'wan6' is setting up now
Mon Jul 14 16:02:12 2025 daemon.notice netifd: wan (4295): udhcpc: started, v1.36.1
Mon Jul 14 16:02:12 2025 daemon.notice netifd: wan (4295): udhcpc: broadcasting discover
Mon Jul 14 16:02:14 2025 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan.20) XX:XX:XX:XX:XX:XX
Mon Jul 14 16:02:14 2025 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan.20) 192.168.2.2 XX:XX:XX:XX:XX:XX
Mon Jul 14 16:02:14 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.20) 192.168.2.2 XX:XX:XX:XX:XX:XX
Mon Jul 14 16:02:14 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.20) 192.168.2.2 XX:XX:XX:XX:XX:XX Atom
Mon Jul 14 16:02:14 2025 kern.info kernel: [171088.529692] mtk_soc_eth 1e100000.ethernet eth0: Link is Down
Mon Jul 14 16:02:14 2025 daemon.notice netifd: Network device 'eth0' link is down
Mon Jul 14 16:02:14 2025 daemon.notice netifd: Interface 'wan' has link connectivity loss
Mon Jul 14 16:02:14 2025 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Mon Jul 14 16:02:14 2025 daemon.notice netifd: wan (4295): udhcpc: received SIGTERM
Mon Jul 14 16:02:14 2025 daemon.notice netifd: Interface 'wan6' is now down
Mon Jul 14 16:02:14 2025 daemon.notice netifd: wan (4295): udhcpc: entering released state
Mon Jul 14 16:02:14 2025 daemon.notice netifd: wan (4295): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Mon Jul 14 16:02:14 2025 daemon.notice netifd: Interface 'wan' is now down
Mon Jul 14 16:02:17 2025 daemon.notice netifd: Network device 'eth0' link is up
Mon Jul 14 16:02:17 2025 daemon.notice netifd: Interface 'wan' has link connectivity
Mon Jul 14 16:02:17 2025 daemon.notice netifd: Interface 'wan' is setting up now
Mon Jul 14 16:02:17 2025 kern.info kernel: [171091.649693] mtk_soc_eth 1e100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Mon Jul 14 16:02:17 2025 daemon.notice netifd: Interface 'wan6' has link connectivity
Mon Jul 14 16:02:17 2025 daemon.notice netifd: Interface 'wan6' is setting up now
Mon Jul 14 16:02:17 2025 daemon.notice netifd: wan (4536): udhcpc: started, v1.36.1
Mon Jul 14 16:02:18 2025 daemon.notice netifd: wan (4536): udhcpc: broadcasting discover
Mon Jul 14 16:02:21 2025 daemon.notice netifd: wan (4536): udhcpc: broadcasting discover
Mon Jul 14 16:02:21 2025 daemon.notice netifd: wan (4536): udhcpc: broadcasting select for 151.XX.X33.251, server 151.XX.X33.252
Mon Jul 14 16:02:21 2025 daemon.notice netifd: wan (4536): udhcpc: lease of 151.XX.X33.251 obtained from 151.XX.X33.252, lease time 120000
Mon Jul 14 16:02:21 2025 daemon.notice netifd: Interface 'wan' is now up
Mon Jul 14 16:02:21 2025 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Mon Jul 14 16:02:21 2025 daemon.info dnsmasq[1]: using nameserver 8.8.8.8#53
Mon Jul 14 16:02:21 2025 daemon.info dnsmasq[1]: using nameserver 8.8.4.4#53
Mon Jul 14 16:02:21 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test
Mon Jul 14 16:02:21 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Mon Jul 14 16:02:21 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Mon Jul 14 16:02:21 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local
Mon Jul 14 16:02:21 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Mon Jul 14 16:02:21 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Mon Jul 14 16:02:21 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Mon Jul 14 16:02:21 2025 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Mon Jul 14 16:02:28 2025 daemon.notice netifd: wan6 (4535): cat: write error: Broken pipe
Mon Jul 14 16:02:28 2025 daemon.notice netifd: Interface 'wan6' is now up
Mon Jul 14 16:02:28 2025 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Mon Jul 14 16:02:28 2025 daemon.info dnsmasq[1]: using nameserver 8.8.8.8#53
Mon Jul 14 16:02:28 2025 daemon.info dnsmasq[1]: using nameserver 8.8.4.4#53
Mon Jul 14 16:02:28 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test
Mon Jul 14 16:02:28 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Mon Jul 14 16:02:28 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Mon Jul 14 16:02:28 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local
Mon Jul 14 16:02:28 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Mon Jul 14 16:02:28 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Mon Jul 14 16:02:28 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Mon Jul 14 16:02:28 2025 user.notice firewall: Reloading firewall due to ifup of wan6 (eth0)
Mon Jul 14 16:02:29 2025 daemon.warn odhcpd[1436]: No default route present, overriding ra_lifetime!
Mon Jul 14 16:02:29 2025 daemon.warn odhcpd[1436]: No default route present, overriding ra_lifetime!
Mon Jul 14 16:06:26 2025 daemon.warn odhcpd[1436]: No default route present, overriding ra_lifetime!
Mon Jul 14 16:10:32 2025 daemon.warn odhcpd[1436]: No default route present, overriding ra_lifetime!
Mon Jul 14 16:20:23 2025 daemon.warn odhcpd[1436]: No default route present, overriding ra_lifetime!
Mon Jul 14 16:25:10 2025 daemon.warn odhcpd[1436]: No default route present, overriding ra_lifetime!
So problem is link down, i suspect it is caused by CPE (that intentionally do it when ISP force an IP change), but what is weird is that it is happening too often (after 4hours, than 1 hours, than maybe 12hours), when it should happen each 24 hours. Maybe i need to speak with my ISP.
Anyway today i had a missing connectivity with my phone, taked timestamp and checked log:
Mon Jul 14 20:17:34 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.30) 192.168.3.33 60:07:c4:de:2b:45
Mon Jul 14 20:17:34 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.30) 192.168.3.33 60:07:c4:de:2b:45 ANTONYPHONE
It should not be a problem, but i had missing connectivity. Looking at my phone, these dhcprerquest are not too much?
Mon Jul 14 11:34:12 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX
Mon Jul 14 11:34:12 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX AntonyPHONE
Mon Jul 14 13:05:11 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX
Mon Jul 14 13:05:11 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX AntonyPHONE
Mon Jul 14 13:23:19 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX
Mon Jul 14 13:23:19 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX AntonyPHONE
Mon Jul 14 13:50:10 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX
Mon Jul 14 13:50:10 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX AntonyPHONE
Mon Jul 14 14:08:02 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX
Mon Jul 14 14:08:02 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX AntonyPHONE
Mon Jul 14 15:26:55 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX
Mon Jul 14 15:26:55 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX AntonyPHONE
Mon Jul 14 17:14:52 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX
Mon Jul 14 17:14:52 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX AntonyPHONE
Mon Jul 14 18:06:14 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX
Mon Jul 14 18:06:14 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX AntonyPHONE
Mon Jul 14 18:59:38 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX
Mon Jul 14 18:59:38 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX AntonyPHONE
Mon Jul 14 20:17:34 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX
Mon Jul 14 20:17:34 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan.30) 192.168.3.33 XX:XX:XX:XX:XX:XX AntonyPHONE
Yup. Link down is indeed the initiating behavior.
Pro-actively, you can replace the cable with one that is known good, just in case you have a marginal cable that is responsible for the link loss. While not terribly likely to be the root cause, it's worth doing this to, at the very lease, exclude a cable issue from the possible culprits (and it is still possible that it will actually be the problem).
Likewise, inspect the ports on both sides to ensure that there are no bent pins or debris.
If you have an ethernet switch lying around, you could always insert it between the CPE and your router. If this resolves the link-down issue on the router, that shows that it is a CPE issue (in rare situations, it can be the ethernet phy betwen the two specific devices that is unhappy). You might even be able to catch the link-down events on the CPE side (either by seeing the link light glitch, or if you have a managed switch, in the logs you'll be able to see that link state change).
But yes, otherwise, talk to your ISP.
These are not problematic. Assuming your DHCP lease time is much longer than 2x what you see here, chances are that this is the phone's wifi hardware sleeping/waking and checking to verify that the lease is still valid (technically not required, but common/good practice for wifi devices to do this).