TP-Link M4R 1.5.8 firmware constantly crashing

TP-Link M4R 1.5.8 firmware constantly crashing

TP-Link M4R 1.5.8 firmware constantly crashing
TP-Link M4R 1.5.8 firmware constantly crashing
2024-02-12 11:31:26 - last edited 2024-02-18 02:26:48
Model: Deco M4  
Hardware Version: V2
Firmware Version: 1.5.8 Build 20230619 Rel. 48552

Recently, my Deco network started to crash quite frequently (10-15 times a day); it lost the connection for 1-2 minutes, and afterwards, it returned to normal.
I changed the network cable and tested it with another ISP Modem.
I tried it too, https://community.tp-link.com/en/home/kb/detail/412552
I don't have more clues to solve it.

 

Mon Feb 12 11:03:44 2024 user.notice dhcpv6: start dial, iface=br-wan

Mon Feb 12 11:03:45 2024 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block

Mon Feb 12 11:03:48 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:03:48 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:03:48 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:03:48 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:03:48 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:03:48 2024 daemon.err nrd[5246]: send ioctl failed

Mon Feb 12 11:03:49 2024 daemon.notice netifd: Network device 'br-wan' link is down

Mon Feb 12 11:03:49 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss

Mon Feb 12 11:03:49 2024 daemon.notice netifd: Interface 'wanv6' has link connectivity loss

Mon Feb 12 11:03:49 2024 daemon.notice conn-indicator: Connectivity changed: ONLINE(0x0) -> OFFLINE(0x1)

Mon Feb 12 11:03:49 2024 user.notice dhcpv6: teardown, interface=wanv6 ifname=br-wan

Mon Feb 12 11:03:49 2024 user.notice dhcpv6: teardown, ip -6 route del ::/0 dev br-wan

Mon Feb 12 11:03:49 2024 daemon.notice netifd: wanv6 (12586): dhcp6_ctl_init 94 addr = ::1, port = 5546

Mon Feb 12 11:03:49 2024 daemon.notice netifd: wanv6 (12586): dhcp6_ctl_init 143 dhcp6_ctl_init succeed

Mon Feb 12 11:03:49 2024 daemon.notice netifd: wanv6 (12586): client6_init 461 client6_init succeed

Mon Feb 12 11:03:50 2024 daemon.notice netifd: Interface 'wanv6' is now down

Mon Feb 12 11:03:53 2024 daemon.err udhcpd[5750]: Sending ACK to 192.168.68.102

Mon Feb 12 11:03:53 2024 daemon.err udhcpd[5750]: clear ip c0a84466

Mon Feb 12 11:03:54 2024 daemon.notice netifd: Network device 'br-wan' link is up

Mon Feb 12 11:03:54 2024 daemon.notice netifd: Interface 'wan' has link connectivity

Mon Feb 12 11:03:54 2024 daemon.notice netifd: Interface 'wanv6' has link connectivity

Mon Feb 12 11:03:54 2024 daemon.notice netifd: Interface 'wanv6' is setting up now

Mon Feb 12 11:03:54 2024 daemon.notice conn-indicator: Connectivity changed: OFFLINE(0x1) -> ONLINE(0x0)

Mon Feb 12 11:03:54 2024 user.notice dhcpv6: start dial, iface=br-wan

Mon Feb 12 11:03:56 2024 user.notice IMPROXY: INFO[imp_input_report_mldv2@461]: MLD_MODE_IS_EXCLUDE

Mon Feb 12 11:03:56 2024 user.notice IMPROXY: INFO[imp_input_report_mldv2@461]: MLD_MODE_IS_EXCLUDE

Mon Feb 12 11:03:58 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:03:58 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:03:58 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:03:58 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:03:58 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:03:59 2024 daemon.notice netifd: Network device 'br-wan' link is down

Mon Feb 12 11:03:59 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss

Mon Feb 12 11:03:59 2024 daemon.notice netifd: Interface 'wanv6' has link connectivity loss

Mon Feb 12 11:03:59 2024 daemon.notice conn-indicator: Connectivity changed: ONLINE(0x0) -> OFFLINE(0x1)

Mon Feb 12 11:03:59 2024 user.notice dhcpv6: teardown, interface=wanv6 ifname=br-wan

Mon Feb 12 11:03:59 2024 user.notice dhcpv6: teardown, ip -6 route del ::/0 dev br-wan

Mon Feb 12 11:03:59 2024 daemon.notice netifd: wanv6 (13294): dhcp6_ctl_init 94 addr = ::1, port = 5546

Mon Feb 12 11:03:59 2024 daemon.notice netifd: wanv6 (13294): dhcp6_ctl_init 143 dhcp6_ctl_init succeed

Mon Feb 12 11:03:59 2024 daemon.notice netifd: wanv6 (13294): client6_init 461 client6_init succeed

Mon Feb 12 11:04:00 2024 daemon.notice netifd: Interface 'wanv6' is now down

Mon Feb 12 11:04:03 2024 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF

Mon Feb 12 11:04:04 2024 daemon.notice netifd: Network device 'br-wan' link is up

Mon Feb 12 11:04:04 2024 daemon.notice netifd: Interface 'wan' has link connectivity

Mon Feb 12 11:04:04 2024 daemon.notice netifd: Interface 'wanv6' has link connectivity

Mon Feb 12 11:04:04 2024 daemon.notice netifd: Interface 'wanv6' is setting up now

Mon Feb 12 11:04:04 2024 daemon.notice conn-indicator: Connectivity changed: OFFLINE(0x1) -> ONLINE(0x0)

Mon Feb 12 11:04:04 2024 user.notice dhcpv6: start dial, iface=br-wan

Mon Feb 12 11:04:08 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:04:08 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:04:08 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:04:08 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:04:08 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:04:09 2024 daemon.notice netifd: Network device 'br-wan' link is down

Mon Feb 12 11:04:09 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss

Mon Feb 12 11:04:09 2024 daemon.notice netifd: Interface 'wanv6' has link connectivity loss

Mon Feb 12 11:04:09 2024 daemon.notice conn-indicator: Connectivity changed: ONLINE(0x0) -> OFFLINE(0x1)

Mon Feb 12 11:04:09 2024 user.notice dhcpv6: teardown, interface=wanv6 ifname=br-wan

Mon Feb 12 11:04:09 2024 user.notice dhcpv6: teardown, ip -6 route del ::/0 dev br-wan

Mon Feb 12 11:04:09 2024 daemon.notice netifd: wanv6 (14018): dhcp6_ctl_init 94 addr = ::1, port = 5546

Mon Feb 12 11:04:09 2024 daemon.notice netifd: wanv6 (14018): dhcp6_ctl_init 143 dhcp6_ctl_init succeed

Mon Feb 12 11:04:09 2024 daemon.notice netifd: wanv6 (14018): client6_init 461 client6_init succeed

Mon Feb 12 11:04:10 2024 daemon.notice netifd: Interface 'wanv6' is now down

Mon Feb 12 11:04:13 2024 daemon.notice netifd: Network device 'br-wan' link is up

Mon Feb 12 11:04:13 2024 daemon.notice netifd: Interface 'wan' has link connectivity

Mon Feb 12 11:04:13 2024 daemon.notice netifd: Interface 'wanv6' has link connectivity

Mon Feb 12 11:04:13 2024 daemon.notice netifd: Interface 'wanv6' is setting up now

Mon Feb 12 11:04:13 2024 daemon.notice conn-indicator: Connectivity changed: OFFLINE(0x1) -> ONLINE(0x0)

Mon Feb 12 11:04:13 2024 user.notice dhcpv6: start dial, iface=br-wan

Mon Feb 12 11:04:13 2024 daemon.err nrd[5246]: send ioctl failed

Mon Feb 12 11:04:18 2024 daemon.notice netifd: Network device 'br-wan' link is down

Mon Feb 12 11:04:18 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss

Mon Feb 12 11:04:18 2024 daemon.notice netifd: Interface 'wanv6' has link connectivity loss

Mon Feb 12 11:04:18 2024 daemon.notice conn-indicator: Connectivity changed: ONLINE(0x0) -> OFFLINE(0x1)

Mon Feb 12 11:04:18 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:04:18 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:04:18 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:04:18 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:04:18 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:04:18 2024 user.notice dhcpv6: teardown, interface=wanv6 ifname=br-wan

Mon Feb 12 11:04:18 2024 user.notice dhcpv6: teardown, ip -6 route del ::/0 dev br-wan

Mon Feb 12 11:04:18 2024 daemon.notice netifd: wanv6 (14913): dhcp6_ctl_init 94 addr = ::1, port = 5546

Mon Feb 12 11:04:18 2024 daemon.notice netifd: wanv6 (14913): dhcp6_ctl_init 143 dhcp6_ctl_init succeed

Mon Feb 12 11:04:18 2024 daemon.notice netifd: wanv6 (14913): client6_init 461 client6_init succeed

Mon Feb 12 11:04:20 2024 daemon.notice netifd: Interface 'wanv6' is now down

Mon Feb 12 11:04:23 2024 daemon.notice netifd: Network device 'br-wan' link is up

Mon Feb 12 11:04:23 2024 daemon.notice netifd: Interface 'wan' has link connectivity

Mon Feb 12 11:04:23 2024 daemon.notice netifd: Interface 'wanv6' has link connectivity

Mon Feb 12 11:04:23 2024 daemon.notice netifd: Interface 'wanv6' is setting up now

Mon Feb 12 11:04:23 2024 daemon.notice conn-indicator: Connectivity changed: OFFLINE(0x1) -> ONLINE(0x0)

Mon Feb 12 11:04:23 2024 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF

Mon Feb 12 11:04:23 2024 user.notice dhcpv6: start dial, iface=br-wan

Mon Feb 12 11:04:28 2024 daemon.notice netifd: Network device 'br-wan' link is down

Mon Feb 12 11:04:28 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss

Mon Feb 12 11:04:28 2024 daemon.notice netifd: Interface 'wanv6' has link connectivity loss

Mon Feb 12 11:04:28 2024 daemon.notice conn-indicator: Connectivity changed: ONLINE(0x0) -> OFFLINE(0x1)

Mon Feb 12 11:04:28 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail

Mon Feb 12 11:04:28 2024 daemon.err /usr/bin/apsd: nl_wifi_newlink_handle:135: Error: config_index_to_name fail
 

  0      
  0      
#1
Options
1 Accepted Solution
Re:TP-Link M4R 1.5.8 firmware constantly crashing-Solution
2024-02-12 12:58:05 - last edited 2024-02-18 02:26:48

  @leomedmar 

 

These log lines are relevant:

 

Mon Feb 12 11:03:49 2024 daemon.notice conn-indicator: Connectivity changed: ONLINE(0x0) -> OFFLINE(0x1)

Mon Feb 12 11:03:54 2024 daemon.notice conn-indicator: Connectivity changed: OFFLINE(0x1) -> ONLINE(0x0)

 

Everything else is just noise in log files.

 

As far as I can tell from log lines, duration of connection drop is exactly five seconds, almost every time. 

 

When I had similar issues at my house, and I have coaxial (cable) Internet, after I convinced ISP Tech Support to troubleshoot it, they have found that coaxial cable outside my house had cracked insulation. The noise level in cable will exceed acceptable threshold, cable modem will silently reboot itself and restore link for some period of time.

 

Outages I had were happening at random times, but because cable modem reboot always takes about same time my outages had same duration each time.

 

 

 

Recommended Solution
  1  
  1  
#2
Options
2 Reply
Re:TP-Link M4R 1.5.8 firmware constantly crashing-Solution
2024-02-12 12:58:05 - last edited 2024-02-18 02:26:48

  @leomedmar 

 

These log lines are relevant:

 

Mon Feb 12 11:03:49 2024 daemon.notice conn-indicator: Connectivity changed: ONLINE(0x0) -> OFFLINE(0x1)

Mon Feb 12 11:03:54 2024 daemon.notice conn-indicator: Connectivity changed: OFFLINE(0x1) -> ONLINE(0x0)

 

Everything else is just noise in log files.

 

As far as I can tell from log lines, duration of connection drop is exactly five seconds, almost every time. 

 

When I had similar issues at my house, and I have coaxial (cable) Internet, after I convinced ISP Tech Support to troubleshoot it, they have found that coaxial cable outside my house had cracked insulation. The noise level in cable will exceed acceptable threshold, cable modem will silently reboot itself and restore link for some period of time.

 

Outages I had were happening at random times, but because cable modem reboot always takes about same time my outages had same duration each time.

 

 

 

Recommended Solution
  1  
  1  
#2
Options
Re:TP-Link M4R 1.5.8 firmware constantly crashing
2024-02-12 15:31:08

  @Alexandre. Thanks for you comment. I'll call for the ISP to check the fiber link outside my home.

  0  
  0  
#3
Options

Information

Helpful: 0

Views: 197

Replies: 2

Related Articles