DECO M5 V3 Fixed Red Light Issue
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I've been using 3 deco M5s quite happily for months and then suddenly earlier today no wifi.
Look at the main M5 and it has a fixed red light, go to the other two units and fixed red lights.
I turned the two remote units off, I've rebooted the main unit. I've rebooted my internet box. I've factory reset the main unit twice.
Each time after factory reset as soon as I connect the first client it goes back to a fixed red light and its gone.
Any ideas?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Finally got to the bottom of this, essentially my Sky Q box is plugged into the virgin hub and that was somehow causing an issue with the M5. I also have a powerline adapter and my TV plugged in as well with no issues, plugging my computer into the M5 wired cable allowed the computer to connect.
I tried to use catch up on Sky Q and it said no Internet connection, checked and no ip address. Rebooted Sky Q and the unit went green almost immediately.
I've done a factory reset on all the units and rebuilt from scratch I have no issues now. All are on the latest firmware,
So it seems the M5 network adapter is rather delicate and can be knocked out quite easily. So anyone with similar issues try removing items from the wireless network to see whats causing the issue,
- Copy Link
- Report Inappropriate Content
@ToMonkey I have now took one of the other devices and reset that and that does the same thing, once you create the wireless network it goes straight to a red light.
The internet connection is fine, the router is fine, its these points. I've changed the port its connected to, both on the AP itself and on my hub, I've also changed the cable.
Someone must have an idea what this is.
- Copy Link
- Report Inappropriate Content
Here is some of the log, I believe thereis no activity on the network interface of the Deco, I've plugged into several switches and rebuilt, the deco never gets a dynamic IP and if you set a static IP you can never ping, you also get no activity on the switch port.
Its strange that all three of my deco m5's are doing the same thing.
I also upgraded to the latest firmware to rule this out.
Someone else must have this issue,.
Thu Oct 22 10:25:12 2020 user.emerg syslog: uci: Entry not found
Thu Oct 22 10:25:13 2020 user.emerg syslog: uci: Entry not found
Thu Oct 22 10:25:13 2020 user.emerg syslog:
Thu Oct 22 10:25:13 2020 user.emerg syslog: SSDK Init OK!
Thu Oct 22 10:25:13 2020 user.emerg syslog: operate done.
Thu Oct 22 10:25:13 2020 user.emerg syslog:
Thu Oct 22 10:25:13 2020 user.emerg syslog: uci: Entry not found
Thu Oct 22 10:25:13 2020 user.emerg syslog: uci: Entry not found
Thu Oct 22 10:25:13 2020 user.emerg syslog: uci: Entry not found
Thu Oct 22 10:25:13 2020 user.emerg syslog: uci: Entry not found
Thu Oct 22 10:25:14 2020 user.emerg syslog: ln: /dev/caldata: File exists
Thu Oct 22 10:25:14 2020 daemon.notice netifd: Network device 'br-wan' link is up
Thu Oct 22 10:25:14 2020 daemon.notice netifd: Interface 'lan' is setting up now
Thu Oct 22 10:25:14 2020 daemon.notice netifd: Interface 'lan' is now up
Thu Oct 22 10:25:14 2020 daemon.notice netifd: Interface 'lanv6' is setting up now
Thu Oct 22 10:25:14 2020 daemon.notice netifd: Interface 'loopback' is setting up now
Thu Oct 22 10:25:14 2020 daemon.notice netifd: Interface 'loopback' is now up
Thu Oct 22 10:25:14 2020 daemon.notice netifd: Network device 'br-wan' link is down
Thu Oct 22 10:25:14 2020 daemon.notice netifd: Interface 'wan' has link connectivity loss
Thu Oct 22 10:25:14 2020 daemon.notice netifd: Network device 'lo' link is up
Thu Oct 22 10:25:14 2020 daemon.notice netifd: Interface 'lanv6' is now up
Thu Oct 22 10:25:15 2020 user.emerg syslog: backhaul_option is 3
Thu Oct 22 10:25:15 2020 user.emerg syslog: net.bridge.bridge-nf-call-custom = 1
Thu Oct 22 10:25:15 2020 daemon.err awn[1284]: [awnd_init:4918]: plc backhaul can not be enable without plc_attached
Thu Oct 22 10:25:15 2020 daemon.err awn[1284]: [awnd_init:4920]: backhaul_option:1
Thu Oct 22 10:25:15 2020 daemon.err awn[1284]: [awnd_init:4931]: wifi backhaul is enable
Thu Oct 22 10:25:15 2020 daemon.notice awn[1284]: [main:5147]: awnd loaded configure and initialize.
Thu Oct 22 10:25:15 2020 daemon.notice awn[1284]: [awnd_mode_convert:4617]: This device changes mode from NONE to FAP
Thu Oct 22 10:25:15 2020 daemon.notice awn[1284]: [awnd_mode_convert:4619]: The configuration is going into effect.
Thu Oct 22 10:25:15 2020 daemon.notice awn[1284]: [awnd_plc_set_root:1245]: This device became plc root.
Thu Oct 22 10:25:15 2020 daemon.crit awn[1284]: [awnd_update_wifi_tpie:911]: config_generic failed awnd_update_tpie(): ath02[-1]
Thu Oct 22 10:25:15 2020 daemon.crit awn[1284]: [awnd_update_wifi_tpie:911]: config_generic failed awnd_update_tpie(): ath12[-1]
Thu Oct 22 10:25:16 2020 daemon.err /usr/bin/apsd: plc_init:161: Error: scan device
Thu Oct 22 10:25:16 2020 user.notice lanv6: start dial, iface=lanv6 ifname=br-lan
Thu Oct 22 10:25:17 2020 user.emerg syslog: Loading defaults
Thu Oct 22 10:25:17 2020 user.emerg syslog: Loading synflood protection
Thu Oct 22 10:25:17 2020 user.emerg syslog: Adding custom chains
Thu Oct 22 10:25:18 2020 user.emerg syslog: Loading zones
Thu Oct 22 10:25:18 2020 user.emerg syslog: Loading forwardings
Thu Oct 22 10:25:18 2020 user.emerg syslog: Loading rules
Thu Oct 22 10:25:18 2020 user.emerg syslog: Loading redirects
Thu Oct 22 10:25:18 2020 user.emerg syslog: Loading includes
Thu Oct 22 10:25:19 2020 user.emerg syslog: Optimizing conntrack
Thu Oct 22 10:25:19 2020 user.emerg syslog: Loading interfaces
Thu Oct 22 10:25:19 2020 user.notice firewall: adding lan (br-lan) to zone lan
Thu Oct 22 10:25:19 2020 user.notice firewall: adding wan (br-wan) to zone wan
Thu Oct 22 10:25:19 2020 user.notice dhcp6s: stop dhcp6s server
Thu Oct 22 10:25:19 2020 user.notice root: stopping dhcp6s
Thu Oct 22 10:25:20 2020 user.notice dhcp6s: starting dhcp6s server
Thu Oct 22 10:25:20 2020 user.warn dhcp6s: dhcp6s is not running,but pid file is exist.
Thu Oct 22 10:25:20 2020 user.notice root: starting dhcp6s
Thu Oct 22 10:25:20 2020 user.warn dhcp6s: wanv6_conn_status is not connected, do not start dhcp6s now
Thu Oct 22 10:25:20 2020 user.emerg syslog: Loading tpcmd
Thu Oct 22 10:25:20 2020 user.emerg syslog: tp209,504[1502]:
Thu Oct 22 10:25:20 2020 user.notice firewall: lanv6 ifup, start update firewall.
Thu Oct 22 10:25:20 2020 user.emerg syslog: loading basic_security
Thu Oct 22 10:25:23 2020 user.emerg syslog: conntrack v1.4.2 (conntrack-tools): connection tracking table has been emptied.
Thu Oct 22 10:25:23 2020 user.emerg syslog: tp219,606[2453]:
Thu Oct 22 10:25:23 2020 user.emerg syslog: tp219,504[2453]:
Thu Oct 22 10:25:23 2020 user.emerg syslog: tp211,501[2834]:
Thu Oct 22 10:25:24 2020 user.emerg syslog: tp211,501[2834]:
Thu Oct 22 10:25:25 2020 user.emerg syslog: tp211,51[2834]:
Thu Oct 22 10:25:25 2020 user.emerg syslog: tp211,502[2834]:
Thu Oct 22 10:25:25 2020 user.emerg syslog: tp211,1[2834]:
Thu Oct 22 10:25:25 2020 user.emerg syslog: Normal env generate
Thu Oct 22 10:25:25 2020 user.emerg syslog: /etc/rc.common: eval: line 1: __network_device: not found
Thu Oct 22 10:25:25 2020 user.emerg syslog: /etc/rc.common: eval: line 1: __network_device: not found
Thu Oct 22 10:25:25 2020 user.emerg syslog: Flush nat forwarding chain
Thu Oct 22 10:25:25 2020 user.emerg syslog: Warning: Executing wildcard deletion to stay compatible with old scripts.
Thu Oct 22 10:25:25 2020 user.emerg syslog: Explicitly specify the prefix length (192.168.68.1/32) to avoid this warning.
Thu Oct 22 10:25:25 2020 user.emerg syslog: This special behaviour is likely to disappear in further releases,
Thu Oct 22 10:25:25 2020 user.emerg syslog: fix your scripts!
Thu Oct 22 10:25:26 2020 user.err smartip: [lan] key:gw value:192.168.68.1
Thu Oct 22 10:25:26 2020 user.err smartip: [lan] key:lanip value:192.168.68.1
Thu Oct 22 10:25:26 2020 user.err smartip: [lan] key:lantype value:1
Thu Oct 22 10:25:26 2020 user.err smartip: [lan] key:mask value:255.255.255.0
Thu Oct 22 10:25:26 2020 user.warn smartip: [lan] Error: open /sys/class/net//carrier fail
Thu Oct 22 10:25:26 2020 user.warn smartip: [lan] Error: open /sys/class/net//carrier fail
Thu Oct 22 10:25:26 2020 user.emerg syslog: tp279,504[3149]:
Thu Oct 22 10:25:26 2020 user.emerg syslog: /etc/rc.common: /etc/rc.d/S48luarsa_keys_gen: line 10: syntax error: unexpected "}"
Thu Oct 22 10:25:26 2020 user.emerg syslog:
Thu Oct 22 10:25:26 2020 user.err smartip: [lan] open /tmp/is_online error...
Thu Oct 22 10:25:26 2020 user.notice smartip: [lan] keep udhcpc on.
Thu Oct 22 10:25:27 2020 user.emerg syslog: Generating a 2048 bit RSA private key
Thu Oct 22 10:25:27 2020 user.notice smartip: [lan] stop domain_login
Thu Oct 22 10:25:27 2020 user.err smartip: [lan] !!ip addr del!! ip addr del 192.168.68.1 dev br-lan
Thu Oct 22 10:25:27 2020 user.notice smartip: [lan] route del default dev br-lan
Thu Oct 22 10:25:27 2020 daemon.err udhcpc[3266]: udhcpc (v1.22.1) started
Thu Oct 22 10:25:27 2020 user.notice smartip: [lan] start udhcpc
Thu Oct 22 10:25:27 2020 daemon.err udhcpc[3266]: Sending discover...
Thu Oct 22 10:25:28 2020 user.err smartip: [lan] open /tmp/is_online error...
Thu Oct 22 10:25:29 2020 user.err smartip: [lan] open /tmp/is_online error...
Thu Oct 22 10:25:30 2020 daemon.notice netifd: Network device 'ath0' link is up
Thu Oct 22 10:25:30 2020 daemon.notice netifd: Bridge 'br-lan' link is up
Thu Oct 22 10:25:30 2020 daemon.err udhcpc[3266]: Sending discover...
Thu Oct 22 10:25:30 2020 user.err smartip: [lan] open /tmp/is_online error...
Thu Oct 22 10:25:31 2020 user.err smartip: [lan] open /tmp/is_online error...
Thu Oct 22 10:25:32 2020 user.err smartip: [lan] open /tmp/is_online error..
- Copy Link
- Report Inappropriate Content
Good day,
Could you please help me check the following information:
May I know who is your internet service provider and what is the modem number of your internet cable modem(internet box)?
How long have you had the Decos?
When the Deco turned red, the WiFi network disappeared or it was still here but connected no internet?
And when it turned red, would rebooting the main Deco, or internet box temporarily fix the issue, or it had to be reset?
Would there still be any IPV4 address when the Deco turned red?
Could you please send me a private message about your TP-LINK ID and the MAC address of the main router?
Thank you very much.
- Copy Link
- Report Inappropriate Content
Hi
My ISP is Virgin Media, the Hub/Router is a HUB3, this is working fine. I have connections through this.
I have had the Decos for approximate 4-5 months in that period setup was simple and they have worked flawlessley.
Yesterday all 3 of them went to a fixed red light and stopped functioning
I have one currently switched on (they have all been reset) I can connect to the wifi on it but there is no Internet connection.
If I reboot, it just goes straight to red, if I reboot virgin, then power on deco straight to red,
If I factory reset and rebuild its yellow, blinking blue and then as soon as its configured a network, straight red.
If I use DHCP there is no address on the deco after config, if I use static the address is there, however it gives me a 192.168.68.x address from its internal DHCP server
I apologise but I don't know how to send you a message, do you want mac from TP Link or Virgin (Or both). I did try to use a fake mac address on the tp link to no effect.
- Copy Link
- Report Inappropriate Content
Finally got to the bottom of this, essentially my Sky Q box is plugged into the virgin hub and that was somehow causing an issue with the M5. I also have a powerline adapter and my TV plugged in as well with no issues, plugging my computer into the M5 wired cable allowed the computer to connect.
I tried to use catch up on Sky Q and it said no Internet connection, checked and no ip address. Rebooted Sky Q and the unit went green almost immediately.
I've done a factory reset on all the units and rebuilt from scratch I have no issues now. All are on the latest firmware,
So it seems the M5 network adapter is rather delicate and can be knocked out quite easily. So anyone with similar issues try removing items from the wireless network to see whats causing the issue,
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2364
Replies: 6
Voters 0
No one has voted for it yet.