AC2200 Deco M9 Plus ping spikes
So i ordered the Deco M9 Plus ( set of 3 ) yesterday, got it today. Hooked it up and noticed a nice fast network. However..
There are ping spikes round about every 10 seconds. I am sure this has to do with the M9 wifi, because when i connect my Desktop to the nearest Deco by UTP cable i have a perfect connection.
My setup is also very simple :
- I have a 1000/1000Mbps fiber connection in my Genexis Platinum-7840. Wifi is disabled on that router.
- I have 3 Deco M9 Plus. The 1st one is connected by UTP to the Genexis. The 2nd and 3rd are added by using the app. All of them about 5 - 8 meters apart.
Also between my Desktop and the 1st deco there is about 4 meters with a plasterboard wall in between, so that can't be an issue either.
Here is a screenshot when i'm connected to the Deco WiFi. Very obvious spikes.
And after this, i connected my desktop wired to the Deco. Extremely stable connection
My IP / gateway :
It seems to me that this proves there is no problem with my internet connection.
Also it proves that the problem is caused by the WiFi of the M9, since the wired connection to the M9 works perfectly.
I'd like some help, since i ordered this because of the many good reviews and it now turns out i should have read more. Because after googling this issue i found many topics that are describing this problem.
I'm disappointed by this. I don't want to spend my friday evening writing topics about ping spikes. I expect hardware i paid a BUNCH of money for to work properly.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Figured it out.
If anyone else is having this issue it is because your WiFi network card in your desktop automatically keeps looking for the best WiFi network. In many cases ( like in mine ) the quality of the different Deco's ( best reception ) is similar, which will cause your WiFi network card to switch every time.
Fix 1 : There is one way you can fix this in windows :
In your windows cmd, type in
netsh wlan show settings
and one of the last things might say
Auto configuration logic is enabled on interface "Wireless Network Connection"
if that's the case, then type in
netsh wlan set autoconfig enabled=no interface="Wireless Network Connection"
It should respond with
Auto configuration has been disabled on interface "Wireless Network Connection".
If it doesn't, then you might have mistyped your interface=" part. Check in your adapter settings, you might have Wireless Network Connection 2 or 3 etc.
This will definitely stop your wireless card from searching for nearby networks and updating your signal quality when you're not asking it to- which is what is causing the spikes.
You will need to turn it back on if you disconnect or need to be able to find nearby networks again.
Fix 2 : The other obvious solution is to make sure that your desktop always has 1 Deco that gives it the best network, so either place it closer to your desktop. Or place the other Deco it switches to further away.
Hope this helps people with the same problem.
- Copy Link
- Report Inappropriate Content
Figured it out.
If anyone else is having this issue it is because your WiFi network card in your desktop automatically keeps looking for the best WiFi network. In many cases ( like in mine ) the quality of the different Deco's ( best reception ) is similar, which will cause your WiFi network card to switch every time.
Fix 1 : There is one way you can fix this in windows :
In your windows cmd, type in
netsh wlan show settings
and one of the last things might say
Auto configuration logic is enabled on interface "Wireless Network Connection"
if that's the case, then type in
netsh wlan set autoconfig enabled=no interface="Wireless Network Connection"
It should respond with
Auto configuration has been disabled on interface "Wireless Network Connection".
If it doesn't, then you might have mistyped your interface=" part. Check in your adapter settings, you might have Wireless Network Connection 2 or 3 etc.
This will definitely stop your wireless card from searching for nearby networks and updating your signal quality when you're not asking it to- which is what is causing the spikes.
You will need to turn it back on if you disconnect or need to be able to find nearby networks again.
Fix 2 : The other obvious solution is to make sure that your desktop always has 1 Deco that gives it the best network, so either place it closer to your desktop. Or place the other Deco it switches to further away.
Hope this helps people with the same problem.
- Copy Link
- Report Inappropriate Content
Thanks for your update, glad to hear that you figured it out.
Now you can enjoy the internet with the Deco M9 plus.
Thanks for sharing it again. Good day.
- Copy Link
- Report Inappropriate Content
Hi all,
I also have this problem with my laptop. If iconnect to a M9 i get this
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2952ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=73ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=51ms TTL=64
Reply from 192.168.1.1: bytes=32 time=79ms TTL=64
Reply from 192.168.1.1: bytes=32 time=18ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2940ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
I see these spikes every 8 to 12 seconds. my whole internetconnection freezes.
If i connect through cable or an other router i dont have this problem.
So i wonder if this is a problem of the M9. i have the version 2 and i downloaded the firmware 1.2.13, but it did not help.
My wifi is useless right now on my laptop. I took a long cable and plugged it in to properly work.
I hope someone has the same issues as i do and have a solution for me.
I also checked the internet and saw some similar issues but nothing worked
I also tried to connect through an usb wifi adapter, but still the same
I have 2 questions:
Is this a problem of windows 10 or
Is there still something not correct in the TP-link m9 V2?
please help,
Dave
- Copy Link
- Report Inappropriate Content
I also posted this in a M5 thread.
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.
192.168.1.1 = ISP CPE
192.168.0.1 = Deco M9 Plus
Back to back connected.
- Copy Link
- Report Inappropriate Content
@Kevin_Z I have the same problem but with my X60 deco, can someone help me, should I Do the same commands?
- Copy Link
- Report Inappropriate Content
Posted in the M5 topic, but I have the same issue with my M9 Plus v2 ... very frustrating!
https://community.tp-link.com/en/home/forum/topic/171562?replyId=561712
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 3061
Replies: 6