Deco M5 latency to modem/router spikes.
I am experiencing issues with a new Deco setup at home.
I have 3 Deco M5s which have drastically improved the connectivity in my home.
The only issue that I cannot seem to fix (using existing TP-Link support threads) is that the latency coming off of the Decos when communicating to the main router is not consistent and frequently (every 10s or so) will drop connection entirely for a brief moment. It will be fine at 20-25ms and then I can watch the pings and see it steadily climb to 5000ms before going offline and then starting back at 20ms.
It's not noticeable usually when doing general things like surfing or watching a buffered video, but voice calls and video games are nearly un-usable.
Things I have attempted which either don't fix the issue, or stop the Deco from working at all:
- disable DHCP on the ISP's provided modem/router
- switch the deco between router and AP mode.
- reset the deco network and start from scratch
I am not able to bridge the modem/router from the ISP because it disables other services which are controlled by the device (IE: Moca, Tivo)
I have also been testing pings directly wired to and on the wireless provided by the ISP device and everything is fine there.
I attempted to troubleshoot with the ISP but they aren't willing provide assistance when using a third party device.
I can provide any futher information required.
Thank you,
Dave
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I ha e exactly this problem too whee latency is high causing me to drop out of conference calls which is a big issue when I am working from home. M5 x 3 connected to plusnet router all good until firmware upgrade to 1.42 from 1.3.1 and wondering if this caused the latency was great before but can't use this currently.
if I connect to plusnet Wi-Fi all good any help or advice would be great.
- Copy Link
- Report Inappropriate Content
I have upgraded to firmware 1.4.2 now and immediately after I tried a ping test.. same result as before.
Is something being done to address this issue with M5? This mesh system isn't cheap, and it appears to be affecting many users.
- Copy Link
- Report Inappropriate Content
Is there any update on this issue ?
- Copy Link
- Report Inappropriate Content
@Kevin_Z can we either fix this issue or enable a rollback of firmware to the 1.3.x release which worked well ?
Thanks
- Copy Link
- Report Inappropriate Content
Any recent updates with these known issues... I purchased (2) Deco M5 Kits within the last few months one installed at home and then other at work office. BOTH expeierence exactly what users are seeing. It currently is 3/23/2020 and both my units show FW Version 1.4.2 Build 20200116 Rel. 46064. Both of mine are set in ROUTER mode also. Very frustrating when spending this kind of money and the devices work great, until handful of times a day you notice this hang.
I can provide my setup details as well if needed but looks like this is a fairly common issue.
Thanks for everyone's help!
- Copy Link
- Report Inappropriate Content
Same issue here with the P7, I guess I'm going to rerun this and get a powerfull router and 2 repeaters, this is just too much. Sure, it will not be TP-Link.
- Copy Link
- Report Inappropriate Content
I had the same in 2x Deco M5.
Every 10 ping was ~2000.
It seems to me that the system tested, which Deco has a faster response.
It helped me turn off Mesh technology (without checking which router is closer) for this computer.
- Copy Link
- Report Inappropriate Content
@Knut-Magne
Same problem here:
(this was taken just now, via wifi laptop -> Deco - wifi backhail - > Deco - cat6 wired ethernet backhaul - Deco -> ISP CPE.)
boy@MacBook-Pro-van-Boy ~ % traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 6.013 ms 4.264 ms 4.479 ms = Main Deco
2 192.168.0.1 (192.168.0.1) 7.211 ms 8.245 ms 6.910 ms = ISP CPE
^C
boy@MacBook-Pro-van-Boy ~ % ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=63 time=10.095 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=63 time=8.654 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=63 time=7.795 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=63 time=6.776 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=63 time=9.152 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=63 time=9.010 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=63 time=6.170 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=63 time=6.446 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=63 time=135.253 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=63 time=6.673 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=63 time=90.121 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=63 time=111.301 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=63 time=9.261 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=63 time=7.039 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=63 time=8.479 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=63 time=7.844 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=63 time=9.302 ms
^C
--- 192.168.0.1 ping statistics ---
17 packets transmitted, 17 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 6.170/26.434/135.253/40.477 ms
boy@MacBook-Pro-van-Boy ~ % ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=6.665 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=8.318 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=6.501 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=3.777 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=5.159 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=5.664 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=8.416 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=4.803 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=5.318 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=4.693 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=5.767 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=5.250 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=5.186 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=4.729 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=5.287 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=4.275 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=3.951 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=3.908 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=4.506 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=5.909 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=5.550 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=4.330 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=7.638 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=5.306 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=6.732 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=6.277 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=5.892 ms
64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=11.413 ms
64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=5.890 ms
64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=5.316 ms
64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=7.689 ms
64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=5.831 ms
64 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=6.574 ms
64 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=3.502 ms
64 bytes from 192.168.1.1: icmp_seq=34 ttl=64 time=7.333 ms
64 bytes from 192.168.1.1: icmp_seq=35 ttl=64 time=4.848 ms
64 bytes from 192.168.1.1: icmp_seq=36 ttl=64 time=3.888 ms
64 bytes from 192.168.1.1: icmp_seq=37 ttl=64 time=120.325 ms
64 bytes from 192.168.1.1: icmp_seq=38 ttl=64 time=124.846 ms
64 bytes from 192.168.1.1: icmp_seq=39 ttl=64 time=5.582 ms
64 bytes from 192.168.1.1: icmp_seq=40 ttl=64 time=76.638 ms
64 bytes from 192.168.1.1: icmp_seq=41 ttl=64 time=5.926 ms
64 bytes from 192.168.1.1: icmp_seq=42 ttl=64 time=4.720 ms
^C
--- 192.168.1.1 ping statistics ---
43 packets transmitted, 43 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 3.502/12.794/124.846/26.542 ms
Constantly random spikes to 150+ ms with no other big bandwidth consumers in the network.
Even when connecting a super short cable directly to the main deco gives me this problem but like 10 ms less only... still horrible. (not above ping test)
It's almost like the WiFi is fine...but the (main) deco takes too long to proces the packets every now and then.
- Copy Link
- Report Inappropriate Content
I'm using the M9 Plus by the way.
Unless the Deco is seriously giving less prio to ICMP packets but yea it's not like this device is for advanced users so no documentation about that to be found... : [
- Copy Link
- Report Inappropriate Content
There wa s a firmware update today (1.4.2) - but the issue remains.
It appears to be occuring almost always after 10 pings, with one exception where the ping timed out.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 41747
Replies: 86