New M4 causing issues with existing E4
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi,
I have recently upgraded my main deco to M4 to imporove the wifi speed now that i have 300mbps internet.
I am now getting drop outs constantly on all decos with them going red at random times. My M4 is set as the main deco connected to a virgin media hub.
Any ideas why im getting these disconnection issues? on the new deco app i am getting notifications non stop about new devices (That arent actually new and have been connected for years) joining even though notifications are off?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@samharris1993 Hi, Thank you for the feedback.
#on the new deco app I am getting notifications non-stop about new devices (That aren't actually new and have been connected for years) joining even though notifications are off.
I think it might be due to the swap of the new main Deco and somehow the whole mesh system still thought E4 was the main Deco. I will follow up on this issue via email and please check later whether you could get an email from me later.
As for the disconnection issue, How often would it happen within one day?
Do you need to reboot the main M4 to get the LED back to white and restore the internet service?
Please also refer to the suggestions here for more advice(case 1):https://community.tp-link.com/en/home/kb/detail/412552
Best regards.
- Copy Link
- Report Inappropriate Content
Hi!
I also have the same problem as above (just upgraded my main deco to M4 from E4 then create a new network from scratch) but have the same issues (get notif about not so new device joined the network) and randomly have all my decos to blinking red (1-2 per day).
Here's the log that I extracted:
I think it happened around 22:33 to 22:35
- Copy Link
- Report Inappropriate Content
After starting my network from scratch i thought all was ok until 16:58 today it all crashed again with red blinking LED's. The main deco re connects quickly followed by the satellite decos a few minutes later. This is the log below of when the issue occurred.
Tue Nov 8 16:58:20 2022 daemon.err udhcpd[3890]: Received SIGTERM
Tue Nov 8 16:58:20 2022 user.emerg syslog: tp259,503[6072]:
Tue Nov 8 16:58:20 2022 user.emerg syslog: tp259,504[6072]:
Tue Nov 8 16:58:21 2022 daemon.err conn-indicator: [validate_dir] stat(/tmp/sync-server): No such file or directory
Tue Nov 8 16:58:21 2022 daemon.err conn-indicator: Invalid directory: /tmp/sync-server
Tue Nov 8 16:58:21 2022 daemon.err conn-indicator: Failed to watch /tmp/sync-server/mesh_dev_list
Tue Nov 8 16:58:21 2022 daemon.err conn-indicator: Failed to allocate DEV_LIST
Tue Nov 8 16:58:21 2022 daemon.err conn-indicator: Ubus object sync not found
Tue Nov 8 16:58:22 2022 daemon.err conn-indicator: [validate_dir] stat(/tmp/sync-server): No such file or directory
Tue Nov 8 16:58:22 2022 daemon.err conn-indicator: Invalid directory: /tmp/sync-server
Tue Nov 8 16:58:22 2022 daemon.err conn-indicator: Failed to watch /tmp/sync-server/mesh_dev_list
Tue Nov 8 16:58:22 2022 daemon.err conn-indicator: Failed to allocate DEV_LIST
Tue Nov 8 16:58:22 2022 daemon.err udhcpd[6598]: udhcpd (v1.22.1) started
Tue Nov 8 16:58:22 2022 daemon.err udhcpd[6598]: start ip 0xc0a84464, end ip 0xc0a844fa, subnet:0xffffff00
Tue Nov 8 16:58:22 2022 daemon.err conn-indicator: Ubus object sync not found
Tue Nov 8 16:58:22 2022 user.emerg syslog: tp211,501[6117]:
Tue Nov 8 16:58:23 2022 user.crit syslog: ntp check success!!!; errno(2): No such file or directory
Tue Nov 8 16:58:23 2022 daemon.err conn-indicator: [validate_dir] stat(/tmp/sync-server): No such file or directory
Tue Nov 8 16:58:23 2022 daemon.err conn-indicator: Invalid directory: /tmp/sync-server
Tue Nov 8 16:58:23 2022 daemon.err conn-indicator: Failed to watch /tmp/sync-server/mesh_dev_list
Tue Nov 8 16:58:23 2022 daemon.err conn-indicator: Failed to allocate DEV_LIST
Tue Nov 8 16:58:23 2022 daemon.err nrd[5932]: estimatorDot11kIterateCB: Timeout waiting for 802.11k response from A8:FE:9D:B1:FB:29
Tue Nov 8 16:58:23 2022 daemon.err conn-indicator: Ubus object sync not found
Tue Nov 8 16:58:23 2022 user.emerg syslog: /etc/rc.common: line 143: can't create /sys/class/net/wds0/queues/rx-0/rps_cpus: nonexistent directory
Tue Nov 8 16:58:23 2022 user.emerg syslog: /etc/rc.common: line 143: can't create /sys/class/net/wds1/queues/rx-0/rps_cpus: nonexistent directory
Tue Nov 8 16:58:23 2022 user.emerg syslog: /etc/rc.common: line 143: can't create /sys/class/net/wds2/queues/rx-0/rps_cpus: nonexistent directory
Tue Nov 8 16:58:23 2022 user.emerg syslog: /etc/rc.common: line 143: can't create /sys/class/net/wds3/queues/rx-0/rps_cpus: nonexistent directory
Tue Nov 8 16:58:23 2022 user.emerg syslog: /etc/rc.common: line 143: can't create /sys/class/net/wdsi0/queues/rx-0/rps_cpus: nonexistent directory
Tue Nov 8 16:58:23 2022 user.emerg syslog: /etc/rc.common: line 143: can't create /sys/class/net/wdsi1/queues/rx-0/rps_cpus: nonexistent directory
Tue Nov 8 16:58:23 2022 user.emerg syslog: /etc/rc.common: line 143: can't create /sys/class/net/wdsi2/queues/rx-0/rps_cpus: nonexistent directory
Tue Nov 8 16:58:23 2022 user.emerg syslog: /etc/rc.common: line 143: can't create /sys/class/net/wdsi3/queues/rx-0/rps_cpus: nonexistent directory
Tue Nov 8 16:58:23 2022 user.emerg syslog: eth0/eth1 RPS: CPU0/2
Tue Nov 8 16:58:23 2022 user.emerg syslog: MT7621 2Card DBDC AP MODE
Tue Nov 8 16:58:23 2022 user.emerg syslog: tp211,501[6117]:
Tue Nov 8 16:58:24 2022 daemon.err nrd[5932]: wlanifLinkEventsCmnHandleIWEvent:unknown flag
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 419
Replies: 3
Voters 0
No one has voted for it yet.