Deco M5 - Very bad ping

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Deco M5 - Very bad ping

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Deco M5 - Very bad ping
Deco M5 - Very bad ping
2023-05-24 12:00:15 - last edited 2023-05-24 13:10:43
Model: Deco M5  
Hardware Version: V3
Firmware Version: 1.7.0 Build 20230504 Rel. 63624

Hi support,
I have a network of 8pcs of  Deco M5 all in Access Point Mode connected to Cisco SG100-24 Switch, all Deco have 1Gbps,tested all cables using Fluke Network Tester.
Fast Roaming - Disabled

Beam forcing - Disabled

Hardware Version.- Deco M5 3.0 and 3.2

Firmware Version - 1.7.0 Build 20230504 Rel. 63624

 

Problem was also on Firmware Version: Deco M5_1.6.5_Build 20230110

I have very big latency to main router,to any Deco or to any server in network using 2.4 Ghz frequency.
I did all tests 0,5-1m away from Deco, using cables,WiFi 2.4ghz,WiFi 5 Ghz. But only cable had a normal ping.
Very very big pings even nobody connected to Deco except myself.

No any other WiFi networks in the building,all cables 1 Gbps.

You can see all test results below:

 

https://rb.gy/wj7s0

 

Ping from Deco 2.4Ghz to Router(192.168.1.1):

 

C:\Windows\system32>ping 192.168.1.1 -n 20

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=35ms TTL=64
Reply from 192.168.1.1: bytes=32 time=64ms TTL=64
Reply from 192.168.1.1: bytes=32 time=36ms TTL=64
Reply from 192.168.1.1: bytes=32 time=20ms TTL=64
Reply from 192.168.1.1: bytes=32 time=36ms TTL=64
Reply from 192.168.1.1: bytes=32 time=18ms TTL=64
Reply from 192.168.1.1: bytes=32 time=24ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Reply from 192.168.1.1: bytes=32 time=28ms TTL=64
Reply from 192.168.1.1: bytes=32 time=44ms TTL=64
Reply from 192.168.1.1: bytes=32 time=49ms TTL=64
Reply from 192.168.1.1: bytes=32 time=301ms TTL=64
Reply from 192.168.1.1: bytes=32 time=12ms TTL=64
Reply from 192.168.1.1: bytes=32 time=35ms TTL=64
Reply from 192.168.1.1: bytes=32 time=13ms 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=125ms TTL=64
Reply from 192.168.1.1: bytes=32 time=113ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 301ms, Average = 49ms

 

Ping from Deco 2.4Ghz to Main Deco(192.168.1.8):

 

C:\Windows\system32>ping 192.168.1.8 -n 20

Pinging 192.168.1.8 with 32 bytes of data:
Reply from 192.168.1.8: bytes=32 time=19ms TTL=64
Reply from 192.168.1.8: bytes=32 time=6ms TTL=64
Reply from 192.168.1.8: bytes=32 time=34ms TTL=64
Reply from 192.168.1.8: bytes=32 time=11ms TTL=64
Reply from 192.168.1.8: bytes=32 time=30ms TTL=64
Reply from 192.168.1.8: bytes=32 time=11ms TTL=64
Reply from 192.168.1.8: bytes=32 time=16ms TTL=64
Reply from 192.168.1.8: bytes=32 time=339ms TTL=64
Reply from 192.168.1.8: bytes=32 time=15ms TTL=64
Reply from 192.168.1.8: bytes=32 time=33ms TTL=64
Reply from 192.168.1.8: bytes=32 time=247ms TTL=64
Reply from 192.168.1.8: bytes=32 time=79ms TTL=64
Reply from 192.168.1.8: bytes=32 time=272ms TTL=64
Reply from 192.168.1.8: bytes=32 time=34ms TTL=64
Reply from 192.168.1.8: bytes=32 time=15ms TTL=64
Reply from 192.168.1.8: bytes=32 time=51ms TTL=64
Reply from 192.168.1.8: bytes=32 time=37ms TTL=64
Reply from 192.168.1.8: bytes=32 time=18ms TTL=64
Reply from 192.168.1.8: bytes=32 time=18ms TTL=64
Reply from 192.168.1.8: bytes=32 time=89ms TTL=64

Ping statistics for 192.168.1.8:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 339ms, Average = 68ms
 

All the rest of tests:
1. From Switch to Router - 1ms

2. From Switch to Main Deco - 1ms

3. From Deco Ethernet Port to Router - 1ms

4. From Deco Ethernet Port to Main Deco - 1ms

5. From 5Ghz to Router - 1-5 ms,average 3ms

6. From 5Ghz to Main Deco - 2-6ms,average 3ms

 

2.4Ghz

2.4 Ghz - Description

 

5Ghz - Descrption

5 Ghz - Description

 

My office unable to make WhatsApp calls,Zoom meetings and so on.
This already is very very frustrating.
But now at least i'm sure that problem is with Deco M5 - 2.4 Ghz.

Best Regards
  2      
  2      
#1
Options
9 Reply
Re:Deco M5 - Very bad ping
2023-05-25 03:51:49

  @mercenaruss 

Hi, Welcome to the community.

Could you please help me run a test:

1. Temporarily unplug the 7 satellite Deco M5 and only leave the main Deco.

2. Connect to the 2.4ghz and test the ping response again.

 Moreover, could you please also install a Wi-Fi analyzer on the smartphone to check the current wireless signal strength and interference on the same and adjacent channels?

Thank you very much.

Wait for your reply.

best regards.

 

  0  
  0  
#2
Options
Re:Deco M5 - Very bad ping
2023-05-25 07:50:02 - last edited 2023-05-25 07:50:16

@David-TP 

Hello David,
1. Unable to unplug all of them today,but will try on Saturday.
2. I checked with WiFi analyzer the frequency:

      -  One Wireles Printer was broadcasting,so was a overlap,disabled him.

      -  Did a optimizations,channel changed to 2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

This is the current ping on 2.4 Ghz ,from 0,5-1m distance from Main Deco.

 

C:\Windows\system32>ping 192.168.1.1 -n 30

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=214ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=19ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=14ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=20ms TTL=64
Reply from 192.168.1.1: bytes=32 time=24ms TTL=64
Reply from 192.168.1.1: bytes=32 time=22ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=13ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms 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=7ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 214ms, Average = 15ms

 

Any more advices,what can be done? Except testing only with Main Deco?

 

Best Regards
  0  
  0  
#3
Options
Re:Deco M5 - Very bad ping
2023-05-25 10:47:10

New information available.
1. I disconnected 4 Deco's,remain only 5.
2. I changed their locations for minimal overlap.

3. I change Main Deco
 

Problem still there,from any Deco point(Basement,Gr. Floor, 2nd. Floor, Pent House)
Below is scanner information + ping from respective locations:

1st. Location, 1 mtr from Deco, only 2.4 Ghz Enabled.

 

C:\Windows\system32>ping 192.168.1.1 -n 30

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=107ms TTL=64
Reply from 192.168.1.1: bytes=32 time=109ms TTL=64
Reply from 192.168.1.1: bytes=32 time=113ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=23ms TTL=64
Reply from 192.168.1.1: bytes=32 time=17ms TTL=64
Reply from 192.168.1.1: bytes=32 time=19ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=132ms TTL=64
Reply from 192.168.1.1: bytes=32 time=149ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=161ms TTL=64
Reply from 192.168.1.1: bytes=32 time=18ms TTL=64
Reply from 192.168.1.1: bytes=32 time=140ms TTL=64
Reply from 192.168.1.1: bytes=32 time=25ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=221ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=24ms 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=59ms TTL=64
Reply from 192.168.1.1: bytes=32 time=117ms TTL=64
Reply from 192.168.1.1: bytes=32 time=13ms TTL=64
Reply from 192.168.1.1: bytes=32 time=21ms TTL=64
Reply from 192.168.1.1: bytes=32 time=29ms TTL=64
Reply from 192.168.1.1: bytes=32 time=56ms TTL=64
Reply from 192.168.1.1: bytes=32 time=46ms TTL=64
Reply from 192.168.1.1: bytes=32 time=65ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 221ms, Average = 56ms

 

2nd. Location, 0.5 mtr from Deco, only 2.4 Ghz Enabled.

 

 

C:\Windows\system32>ping 192.168.1.1 -n 30

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=14ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=53ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=21ms TTL=64
Reply from 192.168.1.1: bytes=32 time=83ms TTL=64
Reply from 192.168.1.1: bytes=32 time=13ms TTL=64
Reply from 192.168.1.1: bytes=32 time=25ms TTL=64
Reply from 192.168.1.1: bytes=32 time=32ms TTL=64
Reply from 192.168.1.1: bytes=32 time=36ms TTL=64
Reply from 192.168.1.1: bytes=32 time=138ms TTL=64
Reply from 192.168.1.1: bytes=32 time=25ms TTL=64
Reply from 192.168.1.1: bytes=32 time=37ms TTL=64
Reply from 192.168.1.1: bytes=32 time=52ms TTL=64
Reply from 192.168.1.1: bytes=32 time=50ms TTL=64
Reply from 192.168.1.1: bytes=32 time=37ms TTL=64
Reply from 192.168.1.1: bytes=32 time=61ms TTL=64
Reply from 192.168.1.1: bytes=32 time=82ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=94ms TTL=64
Reply from 192.168.1.1: bytes=32 time=88ms TTL=64
Reply from 192.168.1.1: bytes=32 time=89ms TTL=64
Reply from 192.168.1.1: bytes=32 time=114ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=21ms 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

Ping statistics for 192.168.1.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 138ms, Average = 40ms

 

 

3rd. Location, 1.5 mtr from Deco, only 2.4 Ghz Enabled.

 

 

C:\Windows\system32>ping 192.168.1.1 -n 30

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=34ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=64ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=67ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Reply from 192.168.1.1: bytes=32 time=14ms TTL=64
Reply from 192.168.1.1: bytes=32 time=17ms TTL=64
Reply from 192.168.1.1: bytes=32 time=32ms TTL=64
Reply from 192.168.1.1: bytes=32 time=45ms TTL=64
Reply from 192.168.1.1: bytes=32 time=113ms TTL=64
Reply from 192.168.1.1: bytes=32 time=81ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=84ms TTL=64
Reply from 192.168.1.1: bytes=32 time=71ms TTL=64
Reply from 192.168.1.1: bytes=32 time=74ms TTL=64
Reply from 192.168.1.1: bytes=32 time=79ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=105ms TTL=64
Reply from 192.168.1.1: bytes=32 time=79ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=14ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 113ms, Average = 35ms

 

 

Based on this, I'm out of options , really dont know what to do next.

 

Best Regards
  0  
  0  
#4
Options
Re:Deco M5 - Very bad ping
2023-05-26 07:58:19 - last edited 2023-05-26 07:58:48

  @David-TP 
I disconnected all Deco except the Main One,
problem is still the same.
Tried 3 different PC's with different Wireless Card - the same problem.
Tried 2 different Phones,with ping activated on Main Router,the same.

Like i said before,only Ethernet Port on deco give me normal ping to router or servers inside network.

Best Regards
  2  
  2  
#5
Options
Re:Deco M5 - Very bad ping
2023-05-26 08:58:01

  @mercenaruss 

Hi, Thanks for the detailed information.

May I know the expected ping response time you wish to get over 2.4 GHz?

 

Based on your ping test, I can roughly get that:

channel 9 with 8 Deco connected

ping router:

Minimum = 5ms, Maximum = 301ms, Average = 49ms

ping main Deco:

Minimum = 6ms, Maximum = 339ms, Average = 68ms

channel 2 with 8 Deco connected

ping router:

 Minimum = 3ms, Maximum = 214ms, Average = 15ms

channel 4 with 5 Decos connected

ping router

Minimum = 2ms, Maximum = 221ms, Average = 56ms

Minimum = 1ms, Maximum = 138ms, Average = 40ms

Minimum = 2ms, Maximum = 113ms, Average = 35ms

So far, the ping is best when 2.4gh is on channel 2. So it seems like channels 1,7.8 are less crowded around the house.

As we know, 2.4ghz is always crowded since there are only 13 channels for use, and easily affected by other wireless signals, like Bluetooth, and Zigbee on the same frequency. Its ping reply time would not be as good as Ethernet and 5ghz connection. 2.4ghz is not a preferred band for live video or audio meetings.

 

 

Thank you very much.

Best regards.

  0  
  0  
#6
Options
Re:Deco M5 - Very bad ping
2023-05-27 09:15:38

  @David-TP 

 

I expect to have a ping not bigger than 8ms or to be able to setup different channels in different location of Deco.
To be 100% sure i installed 3 another Wi-Fi access points from another manufacturers,results are almost similat to this:

 

C:\Windows\system32>ping 192.168.1.1 -n 30

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=14ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms 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
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=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=17ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 17ms, Average = 4ms

 

So now again i'm not sure whats wrong,if another 3 access point are performing very well,except Deco system.

 

Best Regards
  2  
  2  
#7
Options
Re:Deco M5 - Very bad ping
2023-05-30 06:54:18 - last edited 2023-05-30 06:58:34

  @mercenaruss 

Hi, can you also help me check the current wireless channels on this Wi-Fi Access point?

If it is indeed on a quite different channel, later changing the wireless channels on Deco might help.

At the same time, I would like to forward your case to the senior engineers to see whether they had any other suggestions.

Wait for your reply.

Best regards.

  0  
  0  
#8
Options
Re:Deco M5 - Very bad ping
2023-05-30 07:11:30

  @David-TP 

Hello, after many Network Optimisations, now in on channel 9.

Will connect today directly to router,without switch,but I assume this will not help,because like i said in previous post's that:  if using Ethernet Backhaul port on Deco,i have a very good ping (1-2ms) to router or servers in network. 

 

Best Regards
  0  
  0  
#9
Options
Re:Deco M5 - Very bad ping
2023-05-30 09:19:31

  @mercenaruss 

Hi, Thanks for getting back to me. I might not say it clearly and I was wondering what is the current wireless channel for Wi-Fi access points from another manufacturer on which you could get the following ping test result, not the channel of Deco:

Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 17ms, Average = 4ms

 

best regards.

 

  0  
  0  
#10
Options