I can't seem to get the general opinion on whether it's because of a firmware version issue and that downgrading it will help or something else entirely is the problem...
opened 06:44AM - 09 Mar 23 UTC
bug
### Describe the bug
Bananapi BPI R3 is running as main router (DHCP server) … with adblock, samba4 (nvme ssd), transmission daemon (disabled)
It was running smoothly last few months with longest uptime of 30+ days. Just recently it acted weird, it would disconnect all network clients and stopped respond to ping, ssh, luci login...etc. like every 2 days.
hard restart is only thing that can bring it back online again.
I didn't touched anything or modified any config since its last good run, it just suddenly act like this recently.
**Things I've tried but didn't solve:**
- updated to the latest official snapshot.
- Tried disable adblock, transmission.
UPDATE:
Disconnection just happened again after running for about 12hrs from fresh reboot (latest snapshot).
_REMARK: The disconnection has nothing to do with the overheat or temp related, as my records showed that BPI-R3 only reached 50c average for 48hrs with metal case cover fully closed._
The ethernet (which my PC connected directly to BPI-R3) crashed.
**Complete log since the ERROR:**
```
Thu Mar 9 12:37:44 2023 kern.warn kernel: [53627.423716] ------------[ cut here ]------------
Thu Mar 9 12:37:44 2023 kern.info kernel: [53627.428339] NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 6 timed out
Thu Mar 9 12:37:44 2023 kern.warn kernel: [53627.435303] WARNING: CPU: 1 PID: 0 at dev_watchdog+0x330/0x33c
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.441127] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_objref nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_counter nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mt7915e mt76_connac_lib mt76 mac80211 cfg80211 slhc sfp nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 mdio_i2c libcrc32c crc_ccitt compat crypto_safexcel pwm_fan hwmon i2c_gpio i2c_algo_bit nvme nvme_core autofs4 sha1_generic seqiv md5 des_generic libdes authencesn authenc leds_gpio xhci_plat_hcd xhci_pci xhci_mtk_hcd xhci_hcd gpio_button_hotplug usbcore usb_common
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.512141] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.15.98 #0
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.518129] Hardware name: Bananapi BPI-R3 (DT)
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.522641] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.529581] pc : dev_watchdog+0x330/0x33c
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.533576] lr : dev_watchdog+0x330/0x33c
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.537569] sp : ffffffc00800bdb0
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.540867] x29: ffffffc00800bdb0 x28: 0000000000000140 x27: 00000000ffffffff
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.547984] x26: 0000000000000000 x25: 0000000000000001 x24: ffffff8000e394c0
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.555098] x23: 0000000000000000 x22: 0000000000000001 x21: ffffffc008ad6000
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.562213] x20: ffffff8000e39000 x19: 0000000000000006 x18: ffffffc008aea2e0
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.569328] x17: ffffffc0770dc000 x16: ffffffc00800c000 x15: 00000000000005c7
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.576444] x14: 00000000000001ed x13: ffffffc00800bad8 x12: ffffffc008b422e0
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.583560] x11: 712074696d736e61 x10: ffffffc008b422e0 x9 : 0000000000000000
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.590676] x8 : ffffffc008aea290 x7 : ffffffc008aea2e0 x6 : 0000000000000001
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.597791] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.604905] x2 : 0000000000000040 x1 : 0000000000000004 x0 : 000000000000003f
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.612021] Call trace:
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.614453] dev_watchdog+0x330/0x33c
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.618100] call_timer_fn.constprop.0+0x20/0x80
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.622701] __run_timers.part.0+0x208/0x284
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.626954] run_timer_softirq+0x38/0x70
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.630859] _stext+0x10c/0x28c
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.633986] __irq_exit_rcu+0xdc/0xfc
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.637635] irq_exit+0xc/0x1c
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.640676] handle_domain_irq+0x60/0x8c
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.644585] gic_handle_irq+0x50/0x120
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.648320] call_on_irq_stack+0x28/0x44
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.652227] do_interrupt_handler+0x4c/0x54
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.656393] el1_interrupt+0x2c/0x4c
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.659956] el1h_64_irq_handler+0x14/0x20
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.664037] el1h_64_irq+0x74/0x78
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.667422] arch_cpu_idle+0x14/0x20
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.670983] do_idle+0xc0/0x150
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.674113] cpu_startup_entry+0x20/0x60
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.678019] secondary_start_kernel+0x130/0x140
Thu Mar 9 12:37:44 2023 kern.debug kernel: [53627.682532] __secondary_switched+0x50/0x54
Thu Mar 9 12:37:44 2023 kern.warn kernel: [53627.686701] ---[ end trace 23a15a9fb18fbfa4 ]---
Thu Mar 9 12:37:44 2023 kern.err kernel: [53627.691307] mtk_soc_eth 15100000.ethernet eth0: transmit timed out
Thu Mar 9 12:37:44 2023 kern.info kernel: [53627.830536] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Thu Mar 9 12:37:44 2023 kern.err kernel: [53628.373625] mtk_soc_eth 15100000.ethernet: warm reset failed
Thu Mar 9 12:37:44 2023 kern.info kernel: [53628.392404] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
Thu Mar 9 12:37:44 2023 kern.info kernel: [53628.400792] mtk_soc_eth 15100000.ethernet eth1: configuring for inband/2500base-x link mode
Thu Mar 9 12:37:44 2023 kern.info kernel: [53628.400805] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx
Thu Mar 9 12:38:14 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 08:c7:29:b4:34:26
Thu Mar 9 12:38:14 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: disassociated
Thu Mar 9 12:38:14 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: authenticated
Thu Mar 9 12:38:14 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: associated (aid 1)
Thu Mar 9 12:38:14 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 08:c7:29:b4:34:26 auth_alg=open
Thu Mar 9 12:38:14 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 WPA: pairwise key handshake completed (RSN)
Thu Mar 9 12:38:14 2023 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED 08:c7:29:b4:34:26
Thu Mar 9 12:38:14 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.248 08:c7:29:b4:34:26
Thu Mar 9 12:38:14 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.248 08:c7:29:b4:34:26 Mitchs-iPhone
Thu Mar 9 12:39:06 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:39:06 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Thu Mar 9 12:39:25 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:39:25 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:39:28 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:39:28 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:39:32 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:39:32 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:39:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:39:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:39:57 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:39:57 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:40:11 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:40:11 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Thu Mar 9 12:40:13 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:40:13 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:40:15 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:40:15 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:40:19 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:40:19 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:40:27 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:40:27 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:40:44 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:40:44 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:40:56 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:40:56 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Thu Mar 9 12:40:58 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:40:58 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:00 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:00 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:04 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:04 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:13 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:13 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:29 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:29 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:41 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:41 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Thu Mar 9 12:41:43 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:43 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:45 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:45 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:58 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:41:58 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:42:14 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:42:14 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:44:35 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 04:68:65:8b:ee:f8
Thu Mar 9 12:44:35 2023 daemon.info hostapd: phy1-ap0: STA 04:68:65:8b:ee:f8 IEEE 802.11: disassociated
Thu Mar 9 12:44:37 2023 daemon.info hostapd: phy1-ap0: STA 04:68:65:8b:ee:f8 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Mar 9 12:47:18 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:47:18 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Thu Mar 9 12:47:20 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:47:20 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:47:23 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:47:23 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 12:51:37 2023 daemon.info hostapd: phy1-ap0: STA 48:87:59:12:c3:a3 IEEE 802.11: authenticated
Thu Mar 9 12:51:37 2023 daemon.info hostapd: phy1-ap0: STA 48:87:59:12:c3:a3 IEEE 802.11: associated (aid 2)
Thu Mar 9 12:51:37 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 48:87:59:12:c3:a3 auth_alg=open
Thu Mar 9 12:51:37 2023 daemon.info hostapd: phy1-ap0: STA 48:87:59:12:c3:a3 WPA: pairwise key handshake completed (RSN)
Thu Mar 9 12:51:37 2023 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED 48:87:59:12:c3:a3
Thu Mar 9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 48:87:59:12:c3:a3
Thu Mar 9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.148 48:87:59:12:c3:a3
Thu Mar 9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 48:87:59:12:c3:a3
Thu Mar 9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.148 48:87:59:12:c3:a3
Thu Mar 9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 48:87:59:12:c3:a3
Thu Mar 9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.148 48:87:59:12:c3:a3
Thu Mar 9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.148 48:87:59:12:c3:a3
Thu Mar 9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.148 48:87:59:12:c3:a3 2201116SG
Wed Mar 8 23:27:11 2023 daemon.notice procd: /etc/rc.d/S95done: No sensors found!
Wed Mar 8 23:27:11 2023 daemon.notice procd: /etc/rc.d/S95done: Make sure you loaded all the kernel drivers you need.
Wed Mar 8 23:27:11 2023 daemon.notice procd: /etc/rc.d/S95done: Try sensors-detect to find out which these are.
Wed Mar 8 23:27:11 2023 daemon.notice procd: /etc/rc.d/S95done: No sensors found!
Wed Mar 8 23:27:11 2023 daemon.notice procd: /etc/rc.d/S95done: Make sure you loaded all the kernel drivers you need.
Wed Mar 8 23:27:11 2023 daemon.notice procd: /etc/rc.d/S95done: Try sensors-detect to find out which these are.
Wed Mar 8 23:27:11 2023 daemon.info samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
Wed Mar 8 23:27:11 2023 daemon.info samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
Wed Mar 8 23:27:11 2023 daemon.notice procd: /etc/rc.d/S99transmission: Transmission not enabled. Please enable in /etc/config/transmission
Wed Mar 8 23:27:11 2023 daemon.info transmission: Transmission not enabled. Please enable in /etc/config/transmission
Wed Mar 8 23:27:11 2023 daemon.info procd: - init complete -
Wed Mar 8 23:27:13 2023 daemon.notice netifd: wan (2613): udhcpc: broadcasting select for 192.168.1.2, server 192.168.1.1
Wed Mar 8 23:27:13 2023 daemon.notice netifd: wan (2613): udhcpc: lease of 192.168.1.2 obtained from 192.168.1.1, lease time 86400
Wed Mar 8 23:27:13 2023 daemon.notice netifd: Interface 'wan' is now up
Wed Mar 8 23:27:13 2023 user.notice firewall: Reloading firewall due to ifup of wan (br-wan)
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: started, version 2.89 cachesize 1000
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: DNS service limited to local subnets
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: UBus support enabled: connected to system bus
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq-dhcp[1]: DHCP, IP range 192.168.0.100 -- 192.168.0.249, lease time 1h
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using nameserver 1.1.1.1#53
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using nameserver 1.0.0.1#53
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using nameserver 192.168.1.1#53
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: read /etc/hosts - 12 names
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 10 names
Wed Mar 8 23:27:14 2023 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Found user 'nobody' (UID 65534) and group 'nogroup' (GID 65534).
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Successfully dropped root privileges.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: avahi-daemon 0.8 starting up.
Thu Mar 9 13:00:10 2023 daemon.warn avahi-daemon[3566]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: No service file found in /etc/avahi/services.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Joining mDNS multicast group on interface br-wan.IPv6 with address fe80::6826:f2ff:fe1a:acc9.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: New relevant interface br-wan.IPv6 for mDNS.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Joining mDNS multicast group on interface br-wan.IPv4 with address 192.168.1.2.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: New relevant interface br-wan.IPv4 for mDNS.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Joining mDNS multicast group on interface br-lan.IPv6 with address fdc1:bfda:51a1::1.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: New relevant interface br-lan.IPv6 for mDNS.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Joining mDNS multicast group on interface br-lan.IPv4 with address 192.168.0.1.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: New relevant interface br-lan.IPv4 for mDNS.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::6826:f2ff:fe1a:acc8.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: New relevant interface eth0.IPv6 for mDNS.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: New relevant interface lo.IPv6 for mDNS.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: New relevant interface lo.IPv4 for mDNS.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Network interface enumeration completed.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering new address record for fe80::6826:f2ff:fe1a:acc9 on br-wan.*.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering new address record for 192.168.1.2 on br-wan.IPv4.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering new address record for fdc1:bfda:51a1::1 on br-lan.*.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering new address record for 192.168.0.1 on br-lan.IPv4.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering new address record for fe80::6826:f2ff:fe1a:acc8 on eth0.*.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering new address record for ::1 on lo.*.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering new address record for 127.0.0.1 on lo.IPv4.
Thu Mar 9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering HINFO record with values 'AARCH64'/'LINUX'.
Thu Mar 9 13:00:11 2023 daemon.info avahi-daemon[3566]: Server startup complete. Host name is OpenWrt-Bananapi-BPI-R3.local. Local service cookie is 1296436648.
Thu Mar 9 13:00:16 2023 daemon.err nmbd[3166]: [2023/03/09 13:00:16.715866, 0] ../../source3/nmbd/nmbd.c:901(main)
Thu Mar 9 13:00:16 2023 daemon.err nmbd[3166]: nmbd version 4.17.2 started.
Thu Mar 9 13:00:16 2023 daemon.err nmbd[3166]: Copyright Andrew Tridgell and the Samba Team 1992-2022
Thu Mar 9 13:00:17 2023 daemon.err smbd[3165]: [2023/03/09 13:00:17.023557, 0] ../../source3/smbd/server.c:1741(main)
Thu Mar 9 13:00:17 2023 daemon.err smbd[3165]: smbd version 4.17.2 started.
Thu Mar 9 13:00:17 2023 daemon.err smbd[3165]: Copyright Andrew Tridgell and the Samba Team 1992-2022
Thu Mar 9 13:00:39 2023 daemon.err nmbd[3166]: [2023/03/09 13:00:39.751780, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Thu Mar 9 13:00:39 2023 daemon.err nmbd[3166]: *****
Thu Mar 9 13:00:39 2023 daemon.err nmbd[3166]:
Thu Mar 9 13:00:39 2023 daemon.err nmbd[3166]: Samba name server OPENWRT-BANANAPI-BPI-R3 is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.1
Thu Mar 9 13:00:39 2023 daemon.err nmbd[3166]:
Thu Mar 9 13:00:39 2023 daemon.err nmbd[3166]: *****
Thu Mar 9 13:00:40 2023 daemon.info dnsmasq[1]: exiting on receipt of SIGTERM
Thu Mar 9 13:00:49 2023 daemon.info dnsmasq[1]: started, version 2.89 cachesize 1000
Thu Mar 9 13:00:49 2023 daemon.info dnsmasq[1]: DNS service limited to local subnets
Thu Mar 9 13:00:49 2023 daemon.info dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Thu Mar 9 13:00:49 2023 daemon.info dnsmasq[1]: UBus support enabled: connected to system bus
Thu Mar 9 13:00:49 2023 daemon.info dnsmasq-dhcp[1]: DHCP, IP range 192.168.0.100 -- 192.168.0.249, lease time 1h
Thu Mar 9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Thu Mar 9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Thu Mar 9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Thu Mar 9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Thu Mar 9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Thu Mar 9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Thu Mar 9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for zororomemorial.co.zw
Thu Mar 9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for secure.v.co.zw
Thu Mar 9 13:00:49 2023 daemon.info dnsmasq[1]: using 249965 more local addresses
Thu Mar 9 13:00:49 2023 daemon.info dnsmasq[1]: using 369 more nameservers
Thu Mar 9 13:00:50 2023 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Thu Mar 9 13:00:50 2023 daemon.info dnsmasq[1]: using nameserver 1.1.1.1#53
Thu Mar 9 13:00:50 2023 daemon.info dnsmasq[1]: using nameserver 1.0.0.1#53
Thu Mar 9 13:00:50 2023 daemon.info dnsmasq[1]: using nameserver 192.168.1.1#53
Thu Mar 9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Thu Mar 9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Thu Mar 9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Thu Mar 9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Thu Mar 9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Thu Mar 9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Thu Mar 9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for zororomemorial.co.zw
Thu Mar 9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for secure.v.co.zw
Thu Mar 9 13:00:50 2023 daemon.info dnsmasq[1]: using 249965 more local addresses
Thu Mar 9 13:00:50 2023 daemon.info dnsmasq[1]: using 369 more nameservers
Thu Mar 9 13:00:51 2023 daemon.info dnsmasq[1]: read /etc/hosts - 12 names
Thu Mar 9 13:00:51 2023 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 10 names
Thu Mar 9 13:00:51 2023 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Thu Mar 9 13:00:52 2023 user.info adblock-4.1.5[1947]: blocklist with overall 249967 blocked domains loaded successfully (Bananapi BPI-R3, OpenWrt SNAPSHOT r22248-bf055fcdca)
Thu Mar 9 13:01:07 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.203 44:8a:5b:42:23:67
Thu Mar 9 13:01:07 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.203 44:8a:5b:42:23:67 MSI-GP60-LAN
Thu Mar 9 13:01:46 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 9 13:01:46 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
```
### OpenWrt version
r22248-bf055fcdca
### OpenWrt target/subtarget
mediatek filogic
### Device
Bananapi BPI-R3
### Image kind
Official downloaded image
### Steps to reproduce
_No response_
### Actual behaviour
- All client network devices lost connection to DHCP server (Openwrt Bananapi BPI-R3)
- ssh, ping, telnet all got no response from the router.
### Expected behaviour
_No response_
### Additional info
_No response_
### Diffconfig
_No response_
### Terms
- [X] I am reporting an issue for OpenWrt, not an unsupported fork.
opened 09:12PM - 16 Jul 23 UTC
bug
### Describe the bug
While using the router [Zyxel EX5601-T0](https://github.… com/openwrt/openwrt/commit/1c05388ab04c934ec240e8362321908f91381a90) I randomly encountered the following problem:
The Ethernet switch driver (mtk_soc_eth) stops working, for no reason (the crash log is attached in the Actual behavior section).
The following problem seems to be the same as this Issue: #12143
This problem blocks the normal use of the router as well as the functionality of the Ethernet ports.
### OpenWrt version
r23551-e21b4c9636
### OpenWrt target/subtarget
mediatek/filogic
### Device
Zyxel EX5601-T0
### Image kind
Official downloaded image
### Steps to reproduce
_**The mentioned issue is randomly encountered**_, I encountered the issue twice during an active upload stream (for example live video stream) a month apart.
### Actual behaviour
KERNEL LOG:
```
Sun Jul 16 20:31:12 2023 kern.warn kernel: [328426.306756] ------------[ cut here ]------------
Sun Jul 16 20:31:12 2023 kern.info kernel: [328426.311461] NETDEV WATCHDOG: eth1 (mtk_soc_eth): transmit queue 1 timed out
Sun Jul 16 20:31:12 2023 kern.warn kernel: [328426.318517] WARNING: CPU: 2 PID: 0 at dev_watchdog+0x330/0x33c
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.324427] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_objref nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_counter nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mt7915e mt76_connac_lib mt76 mac80211 cfg80211 slhc nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c crc_ccitt compat crypto_safexcel sha1_generic seqiv md5 des_generic libdes authencesn authenc leds_gpio gpio_button_hotplug
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.383717] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 5.15.120 #0
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.389879] Hardware name: Zyxel EX5601-T0 (DT)
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.394478] pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.401505] pc : dev_watchdog+0x330/0x33c
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.405586] lr : dev_watchdog+0x330/0x33c
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.409665] sp : ffffffc008c3bdb0
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.413049] x29: ffffffc008c3bdb0 x28: 0000000000000140 x27: 00000000ffffffff
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.420252] x26: 0000000000000000 x25: 0000000000000002 x24: ffffff800085a4c0
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.427454] x23: 0000000000000000 x22: 0000000000000001 x21: ffffffc008af6000
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.434656] x20: ffffff800085a000 x19: 0000000000000001 x18: ffffffc008b0a338
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.441858] x17: ffffffc0372cf000 x16: ffffffc008c38000 x15: 00000000000005b8
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.449060] x14: 00000000000001e8 x13: ffffffc008c3bad8 x12: ffffffc008b62338
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.456262] x11: 712074696d736e61 x10: ffffffc008b62338 x9 : 0000000000000000
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.463464] x8 : ffffffc008b0a2e8 x7 : ffffffc008b0a338 x6 : 0000000000000001
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.470666] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.477867] x2 : ffffff803fdad080 x1 : ffffffc0372cf000 x0 : 000000000000003f
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.485071] Call trace:
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.487591] dev_watchdog+0x330/0x33c
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.491326] call_timer_fn.constprop.0+0x20/0x80
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.496014] __run_timers.part.0+0x208/0x284
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.500354] run_timer_softirq+0x38/0x70
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.504347] _stext+0x10c/0x28c
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.507559] __irq_exit_rcu+0xdc/0xfc
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.511295] irq_exit+0xc/0x1c
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.514423] handle_domain_irq+0x60/0x8c
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.518420] gic_handle_irq+0x50/0x120
Sun Jul 16 20:31:12 2023 kern.debug kernel: [328426.522244] call_on_irq_stack+0x20/0x34
...
...
...
```
**_Actual behaviour_**
Using the following configuration:
- 2.5 Gbps Fiber ONT is connected on the ETH1 (wan) port (ISP: TIM, Italy).
- A PPoE connection is established through the Fiber ONT on the following router.
- All my devices are wired through the Ethernet ports.
- All client network devices lost connection to DHCP server.
- ssh, ping, telnet all got no response from the router.
Upon crashing, all Ethernet ports stop responding: not allowing me to access the OpenWRT GUI via numeric IP/local DNS name.
I can only access the OpenWRT GUI from the Wi-Fi interface.
(The bug affects the mtk_soc_eth ethernet switch).
To restore full system functionality, I had to completely reboot the router.
### Expected behaviour
The network connectivity should remain stable, and the router should not experience timeouts/crash or loss of LAN access.
### Additional info
The issue occurs randomly and is not reproducible consistently.
The log indicates a timeout in the transmit queue of eth1, which is related to the **Mtk_soc_eth** driver.
Searching the web with the keyword "(mtk_soc_eth): transmit queue" I came across several similar issues.
Except for this problem, the router has never presented any instability problems
I should add that I use Stubby for DoT configuration, I don't think it is the cause of the problem.
### Diffconfig
_No response_
### Terms
- [x] I am reporting an issue for OpenWrt, not an unsupported fork.
I'm on firmware version (23.05.2) it works as intended but under long usage either my WAN cable is bad (?) or one of the options could be causing this issue which I've retrieved from my logs.
Thu Jan 4 09:19:57 2024 kern.info kernel: [26232.293004] mtk_soc_eth 1e100000.ethernet wan: Link is Down
Thu Jan 4 09:19:57 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss
Thu Jan 4 09:19:57 2024 daemon.info pppd[8810]: Terminating on signal 15
Thu Jan 4 09:19:57 2024 daemon.info pppd[8810]: Connect time 399.9 minutes.
Thu Jan 4 09:19:57 2024 daemon.info pppd[8810]: Sent 62449992 bytes, received 844350847 bytes.
Thu Jan 4 09:19:57 2024 daemon.err odhcp6c[9288]: Failed to send RELEASE message to ff02::1:2 (Network unreachable)
Thu Jan 4 09:19:57 2024 daemon.notice netifd: Interface 'wan6' is disabled
Thu Jan 4 09:19:57 2024 daemon.notice netifd: Network device 'pppoe-wan' link is down
Thu Jan 4 09:19:57 2024 daemon.notice netifd: Network alias 'pppoe-wan' link is down
Thu Jan 4 09:19:57 2024 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Thu Jan 4 09:19:57 2024 daemon.notice netifd: wan6 (9288): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan6" } (Permission denied)
Thu Jan 4 09:19:57 2024 daemon.err odhcp6c[9288]: Failed to send SOLICIT message to ff02::1:2 (Network unreachable)
Thu Jan 4 09:19:57 2024 daemon.notice netifd: Interface 'wan6' is now down
Thu Jan 4 09:19:57 2024 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Thu Jan 4 09:19:58 2024 daemon.info dnsmasq[1]: read /etc/hosts - 12 names
Thu Jan 4 09:19:58 2024 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 5 names
Thu Jan 4 09:19:58 2024 daemon.info dnsmasq[1]: read /tmp/hosts/odhcpd - 2 names
Thu Jan 4 09:19:58 2024 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Thu Jan 4 09:19:58 2024 daemon.warn odhcpd[1588]: No default route present, overriding ra_lifetime!
Thu Jan 4 09:20:00 2024 daemon.notice netifd: Network device 'wan' link is up
Thu Jan 4 09:20:00 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Thu Jan 4 09:20:00 2024 kern.info kernel: [26235.412996] mtk_soc_eth 1e100000.ethernet wan: Link is Up - 1Gbps/Full - flow control off
Thu Jan 4 09:20:02 2024 daemon.notice netifd: Interface 'wan' is now down
Thu Jan 4 09:20:02 2024 daemon.notice netifd: Interface 'wan' is setting up now
Thu Jan 4 09:20:02 2024 daemon.info pppd[12302]: Plugin pppoe.so loaded.
Thu Jan 4 09:20:02 2024 daemon.info pppd[12302]: PPPoE plugin from pppd 2.4.9
Thu Jan 4 09:20:02 2024 daemon.notice pppd[12302]: pppd 2.4.9 started by root, uid 0
Thu Jan 4 09:20:18 2024 daemon.warn pppd[12302]: Timeout waiting for PADO packets
Thu Jan 4 09:20:18 2024 daemon.err pppd[12302]: Unable to complete PPPoE Discovery
Thu Jan 4 09:20:18 2024 daemon.info pppd[12302]: Exit.
Thu Jan 4 09:20:18 2024 daemon.notice netifd: Interface 'wan' is now down
Thu Jan 4 09:20:18 2024 daemon.notice netifd: Interface 'wan' is setting up now
Thu Jan 4 09:20:18 2024 daemon.info pppd[12511]: Plugin pppoe.so loaded.
Thu Jan 4 09:20:18 2024 daemon.info pppd[12511]: PPPoE plugin from pppd 2.4.9
Thu Jan 4 09:20:18 2024 daemon.notice pppd[12511]: pppd 2.4.9 started by root, uid 0
Thu Jan 4 09:20:33 2024 daemon.warn pppd[12511]: Timeout waiting for PADO packets
Thu Jan 4 09:20:33 2024 daemon.err pppd[12511]: Unable to complete PPPoE Discovery
Thu Jan 4 09:20:33 2024 daemon.info pppd[12511]: Exit.
Thu Jan 4 09:20:33 2024 daemon.notice netifd: Interface 'wan' is now down
Thu Jan 4 09:20:33 2024 daemon.notice netifd: Interface 'wan' is setting up now
Thu Jan 4 09:20:33 2024 daemon.info pppd[12707]: Plugin pppoe.so loaded.
Thu Jan 4 09:20:33 2024 daemon.info pppd[12707]: PPPoE plugin from pppd 2.4.9
Thu Jan 4 09:20:33 2024 daemon.notice pppd[12707]: pppd 2.4.9 started by root, uid 0
Thu Jan 4 09:20:48 2024 daemon.warn pppd[12707]: Timeout waiting for PADO packets
Thu Jan 4 09:20:48 2024 daemon.err pppd[12707]: Unable to complete PPPoE Discovery
Thu Jan 4 09:20:48 2024 daemon.info pppd[12707]: Exit.
Thu Jan 4 09:20:49 2024 daemon.notice netifd: Interface 'wan' is now down
Thu Jan 4 09:20:49 2024 daemon.notice netifd: Interface 'wan' is setting up now
Thu Jan 4 09:20:49 2024 daemon.info pppd[12903]: Plugin pppoe.so loaded.
Thu Jan 4 09:20:49 2024 daemon.info pppd[12903]: PPPoE plugin from pppd 2.4.9
Thu Jan 4 09:20:49 2024 daemon.notice pppd[12903]: pppd 2.4.9 started by root, uid 0
Thu Jan 4 09:21:04 2024 daemon.warn pppd[12903]: Timeout waiting for PADO packets
Thu Jan 4 09:21:04 2024 daemon.err pppd[12903]: Unable to complete PPPoE Discovery
Thu Jan 4 09:21:04 2024 daemon.info pppd[12903]: Exit.
Thu Jan 4 09:21:04 2024 daemon.notice netifd: Interface 'wan' is now down
Thu Jan 4 09:21:04 2024 daemon.notice netifd: Interface 'wan' is setting up now
Thu Jan 4 09:21:04 2024 daemon.info pppd[13099]: Plugin pppoe.so loaded.
Thu Jan 4 09:21:04 2024 daemon.info pppd[13099]: PPPoE plugin from pppd 2.4.9
Thu Jan 4 09:21:04 2024 daemon.notice pppd[13099]: pppd 2.4.9 started by root, uid 0
Thu Jan 4 09:21:19 2024 daemon.warn pppd[13099]: Timeout waiting for PADO packets
Thu Jan 4 09:21:19 2024 daemon.err pppd[13099]: Unable to complete PPPoE Discovery
Thu Jan 4 09:21:19 2024 daemon.info pppd[13099]: Exit.
Thu Jan 4 09:21:19 2024 daemon.notice netifd: Interface 'wan' is now down
Thu Jan 4 09:21:19 2024 daemon.notice netifd: Interface 'wan' is setting up now
Thu Jan 4 09:21:20 2024 daemon.info pppd[13295]: Plugin pppoe.so loaded.
Thu Jan 4 09:21:20 2024 daemon.info pppd[13295]: PPPoE plugin from pppd 2.4.9
Thu Jan 4 09:21:20 2024 daemon.notice pppd[13295]: pppd 2.4.9 started by root, uid 0
Thu Jan 4 09:21:30 2024 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 24:2e:02:2a:86:05
Thu Jan 4 09:21:30 2024 daemon.info hostapd: phy0-ap0: STA 24:2e:02:2a:86:05 IEEE 802.11: disassociated
Thu Jan 4 09:21:31 2024 daemon.info hostapd: phy0-ap0: STA 24:2e:02:2a:86:05 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Jan 4 09:21:35 2024 daemon.info hostapd: phy0-ap0: STA 24:2e:02:2a:86:05 IEEE 802.11: authenticated
Thu Jan 4 09:21:35 2024 daemon.info hostapd: phy0-ap0: STA 24:2e:02:2a:86:05 IEEE 802.11: associated (aid 5)
Thu Jan 4 09:21:35 2024 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED 24:2e:02:2a:86:05 auth_alg=open
Thu Jan 4 09:21:35 2024 daemon.info hostapd: phy0-ap0: STA 24:2e:02:2a:86:05 WPA: pairwise key handshake completed (RSN)
Thu Jan 4 09:21:35 2024 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED 24:2e:02:2a:86:05
Thu Jan 4 09:21:35 2024 daemon.warn pppd[13295]: Timeout waiting for PADO packets
Thu Jan 4 09:21:35 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 24:2e:02:2a:86:05
Thu Jan 4 09:21:35 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.149 24:2e:02:2a:86:05
Thu Jan 4 09:21:35 2024 daemon.err pppd[13295]: Unable to complete PPPoE Discovery
Thu Jan 4 09:21:35 2024 daemon.info pppd[13295]: Exit.
Thu Jan 4 09:21:35 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.149 24:2e:02:2a:86:05
Thu Jan 4 09:21:35 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.149 24:2e:02:2a:86:05 Honor_Play-67fc820577e153
Thu Jan 4 09:21:35 2024 daemon.notice netifd: Interface 'wan' is now down
Thu Jan 4 09:21:35 2024 daemon.notice netifd: Interface 'wan' is setting up now
Thu Jan 4 09:21:35 2024 daemon.info pppd[13491]: Plugin pppoe.so loaded.
Thu Jan 4 09:21:35 2024 daemon.info pppd[13491]: PPPoE plugin from pppd 2.4.9
Thu Jan 4 09:21:35 2024 daemon.notice pppd[13491]: pppd 2.4.9 started by root, uid 0
Thu Jan 4 09:21:36 2024 daemon.warn odhcpd[1588]: No default route present, overriding ra_lifetime!
Thu Jan 4 09:21:38 2024 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 24:2e:02:2a:86:05
Thu Jan 4 09:21:38 2024 daemon.info hostapd: phy0-ap0: STA 24:2e:02:2a:86:05 IEEE 802.11: disassociated
Thu Jan 4 09:21:38 2024 daemon.info hostapd: phy1-ap0: STA 24:2e:02:2a:86:05 IEEE 802.11: authenticated
Thu Jan 4 09:21:38 2024 daemon.info hostapd: phy1-ap0: STA 24:2e:02:2a:86:05 IEEE 802.11: associated (aid 2)
Thu Jan 4 09:21:38 2024 daemon.notice hostapd: phy0-ap0: Prune association for 24:2e:02:2a:86:05
Thu Jan 4 09:21:38 2024 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 24:2e:02:2a:86:05 auth_alg=open
Thu Jan 4 09:21:38 2024 daemon.info hostapd: phy1-ap0: STA 24:2e:02:2a:86:05 WPA: pairwise key handshake completed (RSN)
Thu Jan 4 09:21:38 2024 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED 24:2e:02:2a:86:05
Thu Jan 4 09:21:39 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 24:2e:02:2a:86:05
Thu Jan 4 09:21:39 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.149 24:2e:02:2a:86:05
Thu Jan 4 09:21:39 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.141 24:2e:02:2a:86:05
Thu Jan 4 09:21:39 2024 daemon.info dnsmasq-dhcp[1]: DHCPNAK(br-lan) 192.168.0.141 24:2e:02:2a:86:05 wrong address
Thu Jan 4 09:21:39 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 24:2e:02:2a:86:05
Thu Jan 4 09:21:39 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.149 24:2e:02:2a:86:05
Thu Jan 4 09:21:39 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.149 24:2e:02:2a:86:05
Thu Jan 4 09:21:39 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.149 24:2e:02:2a:86:05 Honor_Play-67fc820577e153
Thu Jan 4 09:21:40 2024 daemon.warn odhcpd[1588]: No default route present, overriding ra_lifetime!
Thu Jan 4 09:21:45 2024 daemon.info pppd[13491]: PPP session is 1
Thu Jan 4 09:21:45 2024 daemon.warn pppd[13491]: Connected to 00:00:5e:00:01:1e via interface wan
Thu Jan 4 09:21:45 2024 kern.info kernel: [26340.333793] pppoe-wan: renamed from ppp0
Thu Jan 4 09:21:45 2024 daemon.info pppd[13491]: Renamed interface ppp0 to pppoe-wan
Thu Jan 4 09:21:45 2024 daemon.info pppd[13491]: Using interface pppoe-wan
Thu Jan 4 09:21:45 2024 daemon.notice pppd[13491]: Connect: pppoe-wan <--> wan
Thu Jan 4 09:21:48 2024 daemon.info pppd[13491]: Remote message: Access Accept
Thu Jan 4 09:21:48 2024 daemon.notice pppd[13491]: PAP authentication succeeded
When searching the first line of the log the GitHub thread I've linked seems to point out that Software and Hardware offloading seems to cause this...?
I'm also facing a similar issue as this post.
I have a TPLink TL-WDR3600 router. It connects via Ethernet to a VDSL2 modem which connects to a residential phone line. The ISP is Plusnet. The WAN link is via PPPoE, it's configured correctly, it always connects first time. I've had this setup since 2016.
The WAN link can timeout if I max out the connection for a sustained period (I can't do this reliably), or if the ISP side goes silent on me. I've already added config option keepalive '5 5' to the WAN interface (and option pppd_options debu…
After my wan interface is down and comes back up it starts struggling to reconnect to the internet and the log messages keep spamming
Unable to complete PPPoE Discovery
Is there a root cause for this or maybe it's two entirely different issues?
stamak
February 9, 2024, 9:38am
2
FYI: No issues and such kind of logs on my Asus RT-AX53U: OpenWRT 23.05.2 and WAN link is via PPPoE.
PPPoE issues are something entirely different.