Deco M9 disconnects from Internet
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
My setup: modem -> router -> Deco (AP mode) -> devices
I've only had the Deco for 10 days and I upgraded to the latest firmware the same day I got it. Today all of a sudden my devices can no longer connect to Internet. I rebooted my computer and my phone and it didn't help. The WiFi signal is still strong, but no Internet. I loged into the Deco web interface and there's noticable lag and slow response. So I rebooted all the Deco, and my Internet came back. I didn't reboot my modem or router, so the problem was definitely on the Deco.
Does any of you expeience the same thing? With all the WFH going on, I can't have my Internet randomly goes down, this is not acceptable. With my old router it never happens and I never have to worry about my Internet (but it's not a mesh system so it doesn't have the same coverage).
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi,
We have not received any feedback about the firmware issue, we will do some troubleshooting and try to fix it first.
1. What is the LED status on the Deco M9 when there is no internet? BTW, how many Deco M9 units do you have in total, are they all in AP mode?
2. Who is your ISP and what is the model number of this router in front of the Deco M9?
3. How often does it lose connection?
4. What if you connect only one M9 in the network and test its stability?
Good day.
- Copy Link
- Report Inappropriate Content
1. LED is green, I have 2 units, they should both in AP mode. There is only one main unit which you can set router or AP mode, so I don't know what this question meant.
2. ISP is Comcast and Router is Linksys WRT32X.
3. It happens about once a week.
4. I can't test like that for a week I need the second Deco for the internet coverage.
- Copy Link
- Report Inappropriate Content
Hello, thanks for the update.
If the LED on both Deco M9s are solid green, that means they are actually connected to your main router fine, are they both connected to the WRT32X router with cable?
When you mean the internet stops on the Deco network, are all devices showing connected but cannot access the internet? Are they still obtaining the correctly IP address assigned by your WRT32X router? What is the IP subnet?
Is it possible to change the main Deco into Router mode and check if it will improve the current situation?
Please send us the system log by logging into the web UI of the Deco M9 when the internet stops working again and we will analyze further, don't restart it.
Thanks.
- Copy Link
- Report Inappropriate Content
No, only the main Deco is connected to the router with Ethernet cable. The 2nd Deco is on mesh.
Yes, my devices are connected to WiFi but there's no internet connection. IP are 192.168.1.x. I can check again when this happens again.
I go the log while it's running fine, and even then it has a lot of error messages, basically the same error happens every 10 seconds.
Wed Jul 22 15:12:33 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2 Wed Jul 22 15:12:33 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30 Wed Jul 22 15:12:33 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30 Wed Jul 22 15:12:33 2020 user.err csrMeshGw[6596]: CsrMeshMsgQRead: qId=32769 errno=42, No message of desired type!!!! Wed Jul 22 15:12:43 2020 user.err csrMeshGw[6596]: CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff Wed Jul 22 15:12:43 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2 Wed Jul 22 15:12:43 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30 Wed Jul 22 15:12:43 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30 Wed Jul 22 15:12:43 2020 user.err csrMeshGw[6596]: CsrMeshMsgQRead: qId=32769 errno=42, No message of desired type!!!! Wed Jul 22 15:12:53 2020 user.err csrMeshGw[6596]: CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff Wed Jul 22 15:12:53 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2 Wed Jul 22 15:12:53 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30 Wed Jul 22 15:12:53 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30 Wed Jul 22 15:12:53 2020 user.err csrMeshGw[6596]: CsrMeshMsgQRead: qId=32769 errno=42, No message of desired type!!!! Wed Jul 22 15:13:02 2020 daemon.err nrd[6936]: send ioctl failed Wed Jul 22 15:13:03 2020 user.err csrMeshGw[6596]: CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff Wed Jul 22 15:13:03 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2 Wed Jul 22 15:13:03 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30 Wed Jul 22 15:13:03 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30 Wed Jul 22 15:13:03 2020 user.err csrMeshGw[6596]: CsrMeshMsgQRead: qId=32769 errno=42, No message of desired type!!!! Wed Jul 22 15:13:13 2020 user.err csrMeshGw[6596]: CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff Wed Jul 22 15:13:13 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2 Wed Jul 22 15:13:13 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30 Wed Jul 22 15:13:13 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30 Wed Jul 22 15:13:13 2020 user.err csrMeshGw[6596]: CsrMeshMsgQRead: qId=32769 errno=42, No message of desired type!!!! Wed Jul 22 15:13:23 2020 user.err csrMeshGw[6596]: CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff Wed Jul 22 15:13:23 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2 Wed Jul 22 15:13:23 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30 Wed Jul 22 15:13:23 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30 Wed Jul 22 15:13:23 2020 user.err csrMeshGw[6596]: CsrMeshMsgQRead: qId=32769 errno=42, No message of desired type!!!! Wed Jul 22 15:13:30 2020 daemon.err nrd[6936]: send ioctl failed Wed Jul 22 15:13:33 2020 user.err csrMeshGw[6596]: CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff Wed Jul 22 15:13:33 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2 Wed Jul 22 15:13:33 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30 Wed Jul 22 15:13:33 2020 user.err csrMeshGw[6596]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30 Wed Jul 22 15:13:33 2020 user.err csrMeshGw[6596]: CsrMeshMsgQRead: qId=32769 errno=42, No message of desired type!!!! Wed Jul 22 15:13:43 2020 user.err csrMeshGw[6596]:
- Copy Link
- Report Inappropriate Content
Hello, thanks for the update.
For the user.err log display issue, it actually doesn't mean anything that might be abnormal, and it just shows the status of the activities of the Deco devices.
Please send us the log when the internet drops on the Deco later when it is available, thanks.
- Copy Link
- Report Inappropriate Content
@TP-Link_Deco They should turn off the error message if there is no error. Right now it's just spamming the system log. It's hard to find real errors even if something did happen.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1481
Replies: 6
Voters 0
No one has voted for it yet.