BE98 Pro Ping variability over wifi

[proslasher]

I'm seeing pretty drastic ping variability when using wifi on all bands - seemingly randomly. Here's an example that's not as bad as some of the others.

64 bytes from 8.8.8.8: icmp_seq=249 ttl=116 time=8.487 ms
64 bytes from 8.8.8.8: icmp_seq=250 ttl=116 time=10.724 ms
64 bytes from 8.8.8.8: icmp_seq=251 ttl=116 time=7.106 ms
64 bytes from 8.8.8.8: icmp_seq=252 ttl=116 time=9.696 ms
64 bytes from 8.8.8.8: icmp_seq=253 ttl=116 time=7.402 ms
64 bytes from 8.8.8.8: icmp_seq=254 ttl=116 time=9.557 ms
64 bytes from 8.8.8.8: icmp_seq=255 ttl=116 time=11.373 ms
.....
64 bytes from 8.8.8.8: icmp_seq=283 ttl=116 time=7.295 ms
64 bytes from 8.8.8.8: icmp_seq=284 ttl=116 time=25.678 ms
64 bytes from 8.8.8.8: icmp_seq=285 ttl=116 time=15.199 ms
64 bytes from 8.8.8.8: icmp_seq=286 ttl=116 time=8.605 ms
.....

In some cases, I completely see the connection to multiple devices drop with ping spiking to the 2000+ ms yet the ethernet still seems to be okay with a ping in under 4 ms. 

I have the GT98 pro and two GT6 extenders. Wifi signal on the devices does not correlate with dropping the signal. 

Anyone else seeing this issue?

[proslasher]

Here's another snippet of ping going crazy. 

64 bytes from 8.8.8.8: icmp_seq=655 ttl=116 time=7.323 ms
64 bytes from 8.8.8.8: icmp_seq=656 ttl=116 time=7.111 ms
64 bytes from 8.8.8.8: icmp_seq=657 ttl=116 time=7.051 ms
64 bytes from 8.8.8.8: icmp_seq=658 ttl=116 time=8.751 ms
64 bytes from 8.8.8.8: icmp_seq=659 ttl=116 time=29.111 ms
64 bytes from 8.8.8.8: icmp_seq=660 ttl=116 time=12.041 ms
64 bytes from 8.8.8.8: icmp_seq=661 ttl=116 time=7.204 ms
64 bytes from 8.8.8.8: icmp_seq=662 ttl=116 time=7.710 ms

[Saltgrass]

This is how mine are looking right now.  I normally show up around 17-22 and 2 for the deviation.

I did just set my DCHP query frequency from Aggressive to Normal.

I am using copper so if you were to have fiber, they should be lower by quite a bit.  I will try some ping testing using your configuration, and get back.

PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=117 time=8.944 ms
64 bytes from 8.8.8.8: seq=1 ttl=117 time=10.636 ms
64 bytes from 8.8.8.8: seq=2 ttl=117 time=10.486 ms
64 bytes from 8.8.8.8: seq=3 ttl=117 time=10.252 ms
64 bytes from 8.8.8.8: seq=4 ttl=117 time=8.912 ms
64 bytes from 8.8.8.8: seq=5 ttl=117 time=9.733 ms
64 bytes from 8.8.8.8: seq=6 ttl=117 time=10.019 ms
64 bytes from 8.8.8.8: seq=7 ttl=117 time=10.354 ms
64 bytes from 8.8.8.8: seq=8 ttl=117 time=8.649 ms
64 bytes from 8.8.8.8: seq=9 ttl=117 time=8.990 ms

--- 8.8.8.8 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 8.649/9.697/10.636 ms

[proslasher]

Yeah strangely, mine seems to be coming in and out. I'm on fiber, 5gig line to the modem, 1g up and down. Speed isn't an issue at all, the ping variability and random drops of all my devices is the issue. 

I of course can't reproduce this reliably enough to provide a repro; however, I can say that when the devices all drop, ping creeps up a lot. It's not related to a single address (8.8.8.8 or google), and can be repro'ed if I use my local router 192.168.1.254

Reply from 192.168.1.254: bytes=32 time=2ms TTL=63
Reply from 192.168.1.254: bytes=32 time=6ms TTL=63
Reply from 192.168.1.254: bytes=32 time=2ms TTL=63
Reply from 192.168.1.254: bytes=32 time=3ms TTL=63
Reply from 192.168.1.254: bytes=32 time=2ms TTL=63
Reply from 192.168.1.254: bytes=32 time=3ms TTL=63

The one above is from a windows machine on the 6ghz network directly on the router and not the extender. My other was on a 5ghz network. 

Are you also seeing the drops randomly?  

Fwiw - when it drops, everything seems to drop at the same time - cameras, nest home, wife's computer, etc. Ever since I started the ping test it hasn't dropped 😄 

[jzchen]

Sounds like my set up with AT&T BGW320-500?  I just set up with AP mode on the GT-BE98 Pro and seems to be improved overall.  (Let the gateway take some of the workload)…

 

[proslasher]

I think mine is the -505 which is pretty much identical to the 500 but made by a different company?

Either way, yes same setup with the exception of I use router mode and disable AT&Ts built in stuff. 

[proslasher]

Finally got one that actually caused an outage:

64 bytes from 8.8.8.8: icmp_seq=8793 ttl=116 time=10.526 ms
64 bytes from 8.8.8.8: icmp_seq=8794 ttl=116 time=7.049 ms
64 bytes from 8.8.8.8: icmp_seq=8795 ttl=116 time=84.247 ms
64 bytes from 8.8.8.8: icmp_seq=8796 ttl=116 time=34.891 ms
64 bytes from 8.8.8.8: icmp_seq=8797 ttl=116 time=8.756 ms
64 bytes from 8.8.8.8: icmp_seq=8798 ttl=116 time=8.117 ms
64 bytes from 8.8.8.8: icmp_seq=8799 ttl=116 time=7.211 ms
64 bytes from 8.8.8.8: icmp_seq=8800 ttl=116 time=7.496 ms
64 bytes from 8.8.8.8: icmp_seq=8801 ttl=116 time=23.217 ms
64 bytes from 8.8.8.8: icmp_seq=8802 ttl=116 time=6.626 ms
64 bytes from 8.8.8.8: icmp_seq=8803 ttl=116 time=9.858 ms
64 bytes from 8.8.8.8: icmp_seq=8804 ttl=116 time=7.873 ms
64 bytes from 8.8.8.8: icmp_seq=8805 ttl=116 time=9.313 ms
64 bytes from 8.8.8.8: icmp_seq=8806 ttl=116 time=7.656 ms
64 bytes from 8.8.8.8: icmp_seq=8807 ttl=116 time=8.666 ms
64 bytes from 8.8.8.8: icmp_seq=8808 ttl=116 time=8.637 ms
64 bytes from 8.8.8.8: icmp_seq=8809 ttl=116 time=9.887 ms
64 bytes from 8.8.8.8: icmp_seq=8810 ttl=116 time=8.579 ms
64 bytes from 8.8.8.8: icmp_seq=8811 ttl=116 time=9.484 ms
64 bytes from 8.8.8.8: icmp_seq=8812 ttl=116 time=6.270 ms
64 bytes from 8.8.8.8: icmp_seq=8813 ttl=116 time=7.087 ms
64 bytes from 8.8.8.8: icmp_seq=8814 ttl=116 time=8.174 ms
64 bytes from 8.8.8.8: icmp_seq=8815 ttl=116 time=8.238 ms
64 bytes from 8.8.8.8: icmp_seq=8816 ttl=116 time=9.613 ms
64 bytes from 8.8.8.8: icmp_seq=8817 ttl=116 time=7.395 ms
64 bytes from 8.8.8.8: icmp_seq=8818 ttl=116 time=8.315 ms
64 bytes from 8.8.8.8: icmp_seq=8819 ttl=116 time=82.542 ms
64 bytes from 8.8.8.8: icmp_seq=8820 ttl=116 time=25.744 ms
64 bytes from 8.8.8.8: icmp_seq=8821 ttl=116 time=8.820 ms
64 bytes from 8.8.8.8: icmp_seq=8822 ttl=116 time=8.115 ms
64 bytes from 8.8.8.8: icmp_seq=8823 ttl=116 time=7.168 ms
64 bytes from 8.8.8.8: icmp_seq=8824 ttl=116 time=12.362 ms
64 bytes from 8.8.8.8: icmp_seq=8825 ttl=116 time=23.823 ms
64 bytes from 8.8.8.8: icmp_seq=8826 ttl=116 time=8.096 ms
64 bytes from 8.8.8.8: icmp_seq=8827 ttl=116 time=6.569 ms
64 bytes from 8.8.8.8: icmp_seq=8828 ttl=116 time=8.716 ms
64 bytes from 8.8.8.8: icmp_seq=8829 ttl=116 time=6.767 ms
64 bytes from 8.8.8.8: icmp_seq=8830 ttl=116 time=6.768 ms
64 bytes from 8.8.8.8: icmp_seq=8831 ttl=116 time=8.184 ms
64 bytes from 8.8.8.8: icmp_seq=8832 ttl=116 time=7.785 ms
64 bytes from 8.8.8.8: icmp_seq=8833 ttl=116 time=13.013 ms
64 bytes from 8.8.8.8: icmp_seq=8834 ttl=116 time=7.833 ms
64 bytes from 8.8.8.8: icmp_seq=8835 ttl=116 time=10.254 ms

I checked over my ethernet logs at the same time (a raspberry pi running the same ping command) and there's no spike in time - it's right around 4ms despite the wifi spike.

Something is up with the radio or wireless here. 

[proslasher]

Bumping this thread as this is still a significant issue causing my stuff to frequently crash. Asus support, anything you need from me to help diagnose this?

[Saltgrass]

Are you saying something in your ping listings is actually causing your system to crash?  If it is the slow pings, have you seen anything that might coincide with those situations?

Are there any settings in the firmware that might allow the system to ignore or forgive such situations?

Have you checked your router logs at the times when these things happen?

There are many possibilities of problems with an internet connection.  If you were to call your ISP, they should be able to give you advice.

Do you have access to your Modem or Gateway where you can check the possible errors?

When I have problems, the thing I try to do is make my system as simple as possible.  Take it back to a basic configuration.  By doing that, you may eliminate something having configuration errors.

[proslasher]

No, when I say crash, I mean all devices seem to lose internet connectivity for a matter of a minute or two before they come back.  Nothing significant in the logs - this doesn't seem to impact devices that are hardwired to the router. No errors, no data showing that there's even a wifi issue other than my devices dropping signal and ping increasing on ones that don't drop. 

This also doesn't seem to impact the devices that are connected to the AT&T gateway, so this appears to be localized to the BE98 Pro.