Accessibility Resource Center Skip to main content
Have a phone you love? Get up to $500 when you bring your phone.
end of navigation menu

G3100 extremely high pings inside LAN, fast/normal to external destinations

SOLVED
Reply
tommaso
Contributor
Contributor
Posts: 2
Registered: ‎05-28-2022

G3100 extremely high pings inside LAN, fast/normal to external destinations

Message 1 of 4
(723 Views)

This is killing me, I can't understand why there's so much latency on my local network only. For example, here's a ping test from my laptop to, in order, a 1) Chromebook on the same network, 2) iPhone on the same network, 3) the G3100 router, and 4) to google.com:

 

origin machine ==> Macbook Pro
192.168.1.167  ==> Chromebook
192.168.1.153  ==> iPhone 13
192.168.1.1    ==> G3100 router
142.251.40.142 ==> a Google server

➜ ping -c 8 192.168.1.167
PING 192.168.1.167 (192.168.1.167): 56 data bytes
64 bytes from 192.168.1.167: icmp_seq=0 ttl=64 time=492.076 ms
64 bytes from 192.168.1.167: icmp_seq=1 ttl=64 time=204.161 ms
64 bytes from 192.168.1.167: icmp_seq=2 ttl=64 time=132.647 ms
64 bytes from 192.168.1.167: icmp_seq=3 ttl=64 time=42.721 ms
64 bytes from 192.168.1.167: icmp_seq=4 ttl=64 time=375.261 ms
64 bytes from 192.168.1.167: icmp_seq=5 ttl=64 time=190.175 ms
64 bytes from 192.168.1.167: icmp_seq=6 ttl=64 time=106.478 ms
64 bytes from 192.168.1.167: icmp_seq=7 ttl=64 time=26.652 ms

--- 192.168.1.167 ping statistics ---
8 packets transmitted, 8 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 26.652/196.271/492.076/151.697 ms

~ took 7s
➜ ping -c 8 192.168.1.153
PING 192.168.1.153 (192.168.1.153): 56 data bytes
64 bytes from 192.168.1.153: icmp_seq=0 ttl=64 time=59.155 ms
64 bytes from 192.168.1.153: icmp_seq=1 ttl=64 time=78.683 ms
64 bytes from 192.168.1.153: icmp_seq=2 ttl=64 time=102.495 ms
64 bytes from 192.168.1.153: icmp_seq=3 ttl=64 time=22.380 ms
64 bytes from 192.168.1.153: icmp_seq=4 ttl=64 time=41.920 ms
64 bytes from 192.168.1.153: icmp_seq=5 ttl=64 time=66.068 ms
64 bytes from 192.168.1.153: icmp_seq=6 ttl=64 time=89.123 ms
64 bytes from 192.168.1.153: icmp_seq=7 ttl=64 time=109.739 ms

--- 192.168.1.153 ping statistics ---
8 packets transmitted, 8 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 22.380/71.195/109.739/27.960 ms

~ took 7s
➜ ping -c 8 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.328 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=8.152 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=2.597 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=8.083 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=8.020 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=8.090 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.849 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.815 ms

--- 192.168.1.1 ping statistics ---
8 packets transmitted, 8 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.815/5.617/8.152/2.799 ms

~ took 7s
➜ ping -c 8 142.251.40.142
PING 142.251.40.142 (142.251.40.142): 56 data bytes
64 bytes from 142.251.40.142: icmp_seq=0 ttl=118 time=11.663 ms
64 bytes from 142.251.40.142: icmp_seq=1 ttl=118 time=5.587 ms
64 bytes from 142.251.40.142: icmp_seq=2 ttl=118 time=11.633 ms
64 bytes from 142.251.40.142: icmp_seq=3 ttl=118 time=11.442 ms
64 bytes from 142.251.40.142: icmp_seq=4 ttl=118 time=11.631 ms
64 bytes from 142.251.40.142: icmp_seq=5 ttl=118 time=5.101 ms
64 bytes from 142.251.40.142: icmp_seq=6 ttl=118 time=12.146 ms
64 bytes from 142.251.40.142: icmp_seq=7 ttl=118 time=12.044 ms

--- 142.251.40.142 ping statistics ---
8 packets transmitted, 8 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 5.101/10.156/12.146/2.789 ms

 

Here's a similar series of tests from the Chromebook:

 

origin machine ==> Chromebook
192.168.1.152  ==> Macbook Pro
192.168.1.153  ==> iPhone 13
192.168.1.1    ==> G3100 router
142.251.40.142 ==> a Google server

tom@geissler:~$ ping -c 8 192.168.1.152
PING 192.168.1.152 (192.168.1.152) 56(84) bytes of data.
64 bytes from 192.168.1.152: icmp_seq=1 ttl=64 time=2.73 ms
64 bytes from 192.168.1.152: icmp_seq=2 ttl=64 time=14.2 ms
64 bytes from 192.168.1.152: icmp_seq=3 ttl=64 time=3.96 ms
64 bytes from 192.168.1.152: icmp_seq=4 ttl=64 time=59.2 ms
64 bytes from 192.168.1.152: icmp_seq=5 ttl=64 time=81.9 ms
64 bytes from 192.168.1.152: icmp_seq=6 ttl=64 time=202 ms
64 bytes from 192.168.1.152: icmp_seq=7 ttl=64 time=3.07 ms
64 bytes from 192.168.1.152: icmp_seq=8 ttl=64 time=47.5 ms

--- 192.168.1.152 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7010ms
rtt min/avg/max/mdev = 2.730/51.940/202.707/63.479 ms
tom@geissler:~$ ping -c 8 192.168.1.153
PING 192.168.1.153 (192.168.1.153) 56(84) bytes of data.
64 bytes from 192.168.1.153: icmp_seq=1 ttl=64 time=710 ms
64 bytes from 192.168.1.153: icmp_seq=2 ttl=64 time=14.2 ms
64 bytes from 192.168.1.153: icmp_seq=3 ttl=64 time=36.9 ms
64 bytes from 192.168.1.153: icmp_seq=4 ttl=64 time=4.84 ms
64 bytes from 192.168.1.153: icmp_seq=5 ttl=64 time=82.0 ms
64 bytes from 192.168.1.153: icmp_seq=6 ttl=64 time=105 ms
64 bytes from 192.168.1.153: icmp_seq=7 ttl=64 time=24.8 ms
64 bytes from 192.168.1.153: icmp_seq=8 ttl=64 time=46.2 ms

--- 192.168.1.153 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7009ms
rtt min/avg/max/mdev = 4.840/128.071/710.342/222.340 ms
tom@geissler:~$ ping -c 8 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.40 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=3.00 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=2.41 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=4.24 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=4.34 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=4.66 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=4.87 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=4.30 ms

--- 192.168.1.1 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7010ms
rtt min/avg/max/mdev = 1.405/3.657/4.878/1.163 ms
tom@geissler:~$ ping -c 8 142.251.40.142
PING 142.251.40.142 (142.251.40.142) 56(84) bytes of data.
64 bytes from 142.251.40.142: icmp_seq=1 ttl=118 time=4.93 ms
64 bytes from 142.251.40.142: icmp_seq=2 ttl=118 time=9.92 ms
64 bytes from 142.251.40.142: icmp_seq=3 ttl=118 time=6.57 ms
64 bytes from 142.251.40.142: icmp_seq=4 ttl=118 time=8.79 ms
64 bytes from 142.251.40.142: icmp_seq=5 ttl=118 time=8.36 ms
64 bytes from 142.251.40.142: icmp_seq=6 ttl=118 time=8.26 ms
64 bytes from 142.251.40.142: icmp_seq=7 ttl=118 time=8.23 ms
64 bytes from 142.251.40.142: icmp_seq=8 ttl=118 time=8.91 ms

--- 142.251.40.142 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7013ms
rtt min/avg/max/mdev = 4.938/8.001/9.927/1.455 ms

 

And attached are some ping tests from the router to some of the same devices. Better, but still all over the place! What the hell is going on?

 

I don't have that complex of a network setup. Just the single router, some IoT devices which are on the "IoT Network" 2.4GHz only, and the Primary Network had been previously configured with all preset defaults. Since then, I've tried:

 

  1. Disabling SON (band steering)
  2. Disabling WMM (power save)
  3. Disabling QoS
  4. Disabling all 5GHz bands and running all devices over 2.4GHz
  5. Disabling 2.4GHz band and one of the 5GHz bands and running all devices over the remaining 5GHz band
  6. Every combination of the above

Some things made latency worse, but nothing made them better.

 

There are exactly 8 devices on the 2.4 GHz "IoT Network". Some bulbs, an A/C, and a Roomba. I'd be shocked if these were wreaking such havoc as to create that kind of latency between other devices on the LAN

 

Please, help!

 

Screen Shot 2022-05-28 at 15.44.31.pngScreen Shot 2022-05-28 at 15.44.51.pngScreen Shot 2022-05-28 at 15.45.09.png

1 ACCEPTED SOLUTION

Accepted Solutions
Smith6612
Platinum Contributor III Platinum Contributor III
Platinum Contributor III
Posts: 7,635
Registered: ‎12-15-2010

Re: G3100 extremely high pings inside LAN, fast/normal to external destinations

Message 4 of 4
(583 Views)

@tommaso wrote:

It was this all along:

 

https://superuser.com/questions/1713147/high-variable-ping-times-to-machine-on-local-network 

 

Close the thread...


Came here to say this. I've seen this before. Many devices including Smart TVs and Laptops will aggressively power save on the Wi-Fi when they are not actively transmitting data themselves. Make the device transfer data using iperf or something, and see if the latency is steady.

 

You can improve this by lowering the DTIM on the network to 1, but this will also come with potential instability for devices which are VERY aggressive with power saving (Apple devices notably).

View solution in original post

3 REPLIES 3
tommaso
Contributor
Contributor
Posts: 2
Registered: ‎05-28-2022

Re: G3100 extremely high pings inside LAN, fast/normal to external destinations

Message 2 of 4
(675 Views)
Cang_Household
MVP MVP
MVP
Posts: 1,693
Registered: ‎09-06-2020

Re: G3100 extremely high pings inside LAN, fast/normal to external destinations

Message 3 of 4
(661 Views)

So, are you saying this is a problem of the client devices instead of G3100?

Smith6612
Platinum Contributor III Platinum Contributor III
Platinum Contributor III
Posts: 7,635
Registered: ‎12-15-2010

Re: G3100 extremely high pings inside LAN, fast/normal to external destinations

Message 4 of 4
(584 Views)

@tommaso wrote:

It was this all along:

 

https://superuser.com/questions/1713147/high-variable-ping-times-to-machine-on-local-network 

 

Close the thread...


Came here to say this. I've seen this before. Many devices including Smart TVs and Laptops will aggressively power save on the Wi-Fi when they are not actively transmitting data themselves. Make the device transfer data using iperf or something, and see if the latency is steady.

 

You can improve this by lowering the DTIM on the network to 1, but this will also come with potential instability for devices which are VERY aggressive with power saving (Apple devices notably).

How-To Videos
 
The following videos were produced by users like you!
   
Videos are subject to the Verizon Fios Community Terms of Service and User Guidelines and contains content that is not created by Verizon.
Have a spare Fios-G1100?Learn how to bridge it into your network
Get Started


Covid19

Browse Categories
Categories:
Posts

Verizon Troubleshooters
Unable to find your answer here? Try searching Verizon Troubleshooters for more options.
Modal Dialogue Title