Deco M5 red light always, unreliable internet

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Deco M5 red light always, unreliable internet

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Deco M5 red light always, unreliable internet
Deco M5 red light always, unreliable internet
2020-08-03 06:52:04 - last edited 2020-08-03 06:57:00
Model: Deco M5  
Hardware Version: V3
Firmware Version: 1.4.4 Rel 65392

I bought a 3x pack Deco M5s a week ago and they've now stopped working as of yesterday, and the red light on top remains on no matter what I have tried. The green light comes on briefly, then defaults back to red. The internet lags a couple of seconds after requests. The app goes back and forth between "connected to the internet" and not. It's hard to say whether it's actually connected to the internet at any point. My Google Home cannot connect to the internet, which makes it unusable. Both it and the Chromecast keep open 200 connections each.

 

Configuration: Netgear Nighthawk R7000 as main router, Wifi off. Main Deco is connected to a LAN port and set to Access Point. 

 

Tried:

  • Resetting the router
  • Resetting all the Decos multiple times
  • Reset the NBN HFC modem
  • Called the ISP
    • Connection test
    • Kicked the connection/reset
    • Loopback test 
  • Connected directly to the modem as a router
  • downgrading firmware to 1.4.2 (blocked when I try)
  • Swapped out the main deco with one of the others
  • Dynamic and static IPs on the router.
  • Multiple resets

 

Incredibly frustrating. Spent a lot of hours yesterday and today to get absolutely nowhere. This is a consumer product and shouldn't simply collapse to completely useless within a week of purchase. 

 

Here's the log (the time apparently hasn't been able to be set):

 

Fri Feb 21 20:01:40 2020 user.emerg syslog: uci: Entry not found

Fri Feb 21 20:01:40 2020 user.emerg syslog:

Fri Feb 21 20:01:40 2020 user.emerg syslog: SSDK Init OK!

Fri Feb 21 20:01:40 2020 user.emerg syslog: operate done.

Fri Feb 21 20:01:40 2020 user.emerg syslog:

Fri Feb 21 20:01:40 2020 user.emerg syslog: uci: Entry not found

Fri Feb 21 20:01:41 2020 user.emerg syslog: uci: Entry not found

Fri Feb 21 20:01:41 2020 user.emerg syslog: uci: Entry not found

Fri Feb 21 20:01:41 2020 user.emerg syslog: uci: Entry not found

Fri Feb 21 20:01:41 2020 user.emerg syslog: uci: Entry not found

Fri Feb 21 20:01:41 2020 user.emerg syslog: ln: /dev/caldata: File exists

Fri Feb 21 20:01:42 2020 user.emerg syslog: net.bridge.bridge-nf-call-custom = 1

Fri Feb 21 20:01:43 2020 daemon.crit awn[1241]: [awnd_update_wifi_tpie:895]: config_generic failed awnd_update_tpie(): ath02[-1]

Fri Feb 21 20:01:43 2020 daemon.crit awn[1241]: [awnd_update_wifi_tpie:895]: config_generic failed awnd_update_tpie(): ath12[-1]

Fri Feb 21 20:01:43 2020 daemon.err /usr/bin/apsd: plc_init:151: Error: scan device

Fri Feb 21 20:01:44 2020 user.emerg syslog: Loading defaults

Fri Feb 21 20:01:45 2020 user.emerg syslog: Loading synflood protection

Fri Feb 21 20:01:45 2020 user.emerg syslog: Adding custom chains

Fri Feb 21 20:01:45 2020 user.emerg syslog: Loading zones

Fri Feb 21 20:01:46 2020 user.emerg syslog: Loading forwardings

Fri Feb 21 20:01:46 2020 user.emerg syslog: Loading rules

Fri Feb 21 20:01:46 2020 user.emerg syslog: Loading redirects

Fri Feb 21 20:01:46 2020 user.emerg syslog: Loading includes

Fri Feb 21 20:01:46 2020 user.emerg syslog: Optimizing conntrack

Fri Feb 21 20:01:46 2020 user.emerg syslog: Loading interfaces

Fri Feb 21 20:01:47 2020 user.emerg syslog: Loading tpcmd

Fri Feb 21 20:01:48 2020 user.emerg syslog: tp209,504[1443]:

Fri Feb 21 20:01:48 2020 user.emerg syslog: loading basic_security

Fri Feb 21 20:01:51 2020 user.emerg syslog: conntrack v1.4.2 (conntrack-tools): connection tracking table has been emptied.

Fri Feb 21 20:01:51 2020 user.emerg syslog: tp219,606[2340]:

Fri Feb 21 20:01:51 2020 user.emerg syslog: tp219,504[2340]:

Fri Feb 21 20:01:51 2020 user.emerg syslog: tp211,501[2727]:

Fri Feb 21 20:01:51 2020 user.emerg syslog: tp211,501[2727]:

Fri Feb 21 20:01:52 2020 user.emerg syslog: tp211,51[2727]:

Fri Feb 21 20:01:52 2020 user.emerg syslog: tp211,502[2727]:

Fri Feb 21 20:01:52 2020 user.emerg syslog: tp211,1[2727]:

Fri Feb 21 20:01:52 2020 user.emerg syslog: Normal env generate

Fri Feb 21 20:01:52 2020 user.emerg syslog: /etc/rc.common: eval: line 1: __network_device: not found

Fri Feb 21 20:01:52 2020 user.emerg syslog: /etc/rc.common: eval: line 1: __network_device: not found

Fri Feb 21 20:01:53 2020 user.emerg syslog: Flush nat forwarding chain

Fri Feb 21 20:01:53 2020 user.emerg syslog: Warning: Executing wildcard deletion to stay compatible with old scripts.

Fri Feb 21 20:01:53 2020 user.emerg syslog: Explicitly specify the prefix length (192.168.68.1/32) to avoid this warning.

Fri Feb 21 20:01:53 2020 user.emerg syslog: This special behaviour is likely to disappear in further releases,

Fri Feb 21 20:01:53 2020 user.emerg syslog: fix your scripts!

Fri Feb 21 20:01:53 2020 user.err smartip: [lan] key:gw value:192.168.68.1

Fri Feb 21 20:01:53 2020 user.err smartip: [lan] key:lanip value:192.168.68.1

Fri Feb 21 20:01:53 2020 user.err smartip: [lan] key:lantype value:1

Fri Feb 21 20:01:53 2020 user.err smartip: [lan] key:mask value:255.255.255.0

Fri Feb 21 20:01:53 2020 user.emerg syslog: tp279,504[3033]:

Fri Feb 21 20:01:54 2020 user.emerg syslog: /etc/rc.common: /etc/rc.d/S48luarsa_keys_gen: line 10: syntax error: unexpected "}"

Fri Feb 21 20:01:54 2020 user.err smartip: [lan] open /tmp/is_online error...

Fri Feb 21 20:01:54 2020 user.emerg syslog: generate key: 1825 1024

Fri Feb 21 20:01:54 2020 user.err smartip: [lan] !!ip addr del!! ip addr del 192.168.68.1 dev br-lan

Fri Feb 21 20:01:54 2020 daemon.err udhcpc[3146]: udhcpc (v1.22.1) started

Fri Feb 21 20:01:54 2020 daemon.err udhcpc[3146]: Sending discover...

Fri Feb 21 20:01:56 2020 user.err smartip: [lan] open /tmp/is_online error...

Fri Feb 21 20:01:57 2020 user.err smartip: [lan] open /tmp/is_online error...

Fri Feb 21 20:01:57 2020 user.emerg syslog: Sorry, rule does not exist.

Fri Feb 21 20:01:57 2020 user.emerg syslog: Sorry, rule does not exist.

Fri Feb 21 20:01:57 2020 daemon.err udhcpc[3146]: Sending discover...

Fri Feb 21 20:01:58 2020 user.emerg syslog: no private ioctls.

Fri Feb 21 20:01:58 2020 user.emerg syslog:

Fri Feb 21 20:01:58 2020 user.emerg syslog: no private ioctls.

Fri Feb 21 20:01:58 2020 user.emerg syslog:

Fri Feb 21 20:01:58 2020 user.emerg syslog: no private ioctls.

Fri Feb 21 20:01:58 2020 user.emerg syslog:

Fri Feb 21 20:01:58 2020 user.err smartip: [lan] open /tmp/is_online error...

Fri Feb 21 20:01:58 2020 user.emerg syslog: no private ioctls.

Fri Feb 21 20:01:58 2020 user.emerg syslog:

Fri Feb 21 20:01:59 2020 user.err smartip: [lan] open /tmp/is_online error...

Fri Feb 21 20:02:00 2020 user.err smartip: [lan] open /tmp/is_online error...

Fri Feb 21 20:02:00 2020 user.emerg syslog: bluetooth closed

Fri Feb 21 20:02:00 2020 user.emerg syslog: killall: leds_set_nightmode: no process killed

Fri Feb 21 20:02:00 2020 daemon.err udhcpc[3146]: Sending discover...

Fri Feb 21 20:02:01 2020 user.err smartip: [lan] open /tmp/is_online error...

Fri Feb 21 20:02:01 2020 user.emerg syslog: tp269,504[4071]:

Fri Feb 21 20:02:02 2020 daemon.err conn-indicator: [validate_dir] stat(/tmp/sync-server): No such file or directory

Fri Feb 21 20:02:02 2020 daemon.err conn-indicator: Invalid directory: /tmp/sync-server

Fri Feb 21 20:02:02 2020 daemon.err conn-indicator: Failed to watch /tmp/sync-server/mesh_dev_list

Fri Feb 21 20:02:02 2020 daemon.err conn-indicator: Failed to allocate DEV_LIST

Fri Feb 21 20:02:02 2020 user.emerg syslog: cat: can't open '/tmp/tipc_runtime_addr': No such file or directory

Fri Feb 21 20:02:02 2020 user.emerg syslog: cat: can't open '/tmp/tipc_runtime_bear': No such file or directory

Fri Feb 21 20:02:03 2020 daemon.err conn-indicator: [validate_dir] stat(/tmp/sync-server): No such file or directory

Fri Feb 21 20:02:03 2020 daemon.err conn-indicator: Invalid directory: /tmp/sync-server

Fri Feb 21 20:02:03 2020 daemon.err conn-indicator: Failed to watch /tmp/sync-server/mesh_dev_list

Fri Feb 21 20:02:03 2020 daemon.err conn-indicator: Failed to allocate DEV_LIST

Fri Feb 21 20:02:03 2020 user.emerg syslog: (notice) ndppd (NDP Proxy Daemon) version 0.2.4

Fri Feb 21 20:02:03 2020 user.emerg syslog: (notice) Using configuration file '/var/etc/ndppd.conf'

Fri Feb 21 20:02:03 2020 user.emerg syslog: (error) Failed to load configuration file '/var/etc/ndppd.conf'

Fri Feb 21 20:02:04 2020 daemon.err conn-indicator: [validate_dir] stat(/tmp/sync-server): No such file or directory

Fri Feb 21 20:02:04 2020 daemon.err conn-indicator: Invalid directory: /tmp/sync-server

Fri Feb 21 20:02:04 2020 daemon.err conn-indicator: Failed to watch /tmp/sync-server/mesh_dev_list

Fri Feb 21 20:02:04 2020 daemon.err conn-indicator: Failed to allocate DEV_LIST

Fri Feb 21 20:02:04 2020 user.emerg syslog: sh: north-america.pool.ntp.org: unknown operand

Fri Feb 21 20:02:04 2020 daemon.err client_mgmt: wireless client associate or disassociate.

Fri Feb 21 20:02:04 2020 daemon.err client_mgmt: client_mac:88-B2-91-5B-CC-85, client_ifname:ath0, client_action:associate

Fri Feb 21 20:02:04 2020 daemon.err client_mgmt: client(88-B2-91-5B-CC-85) assocaite by if(ath0).

Fri Feb 21 20:02:05 2020 daemon.err client_mgmt: wireless client associate or disassociate.

Fri Feb 21 20:02:05 2020 daemon.err client_mgmt: client_mac:34-EA-34-44-26-89, client_ifname:ath0, client_action:associate

Fri Feb 21 20:02:05 2020 daemon.err client_mgmt: client(34-EA-34-44-26-89) assocaite by if(ath0).

 

  0      
  0      
#1
Options
1 Reply
Re:Deco M5 red light always, unreliable internet
2020-08-03 08:55:00

@CanuckOz 

 

Hello,

 

Do you mean this issue occurs after you perform a firmware update for the Deco system? Was it working fine before with the previous firmware?

 

When you reset the Deco M5, does the reset process go smoothly and the reset is successful? Please only connect the main Deco to the network and try to add it again via the Deco app, then confirm which step did you get stuck with:

https://www.tp-link.com/support/faq/2239/

 

As per the time settings on the Deco system, can you please confirm again what is the System Time setting on your Deco network? You may login to the web interface again and go to System Time, change it to another one then switch back to give it a go, please show me the screenshot again:

https://www.tp-link.com/support/faq/2641/

 

Thanks.

  0  
  0  
#2
Options

Information

Helpful: 0

Views: 2368

Replies: 1

Related Articles