NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Odd ping between satellite and router since 2.5.1.8 update
Ever since updating my orbi RBR50 and RBR 50 to firmware 2.5.1.8 last week, my internet is very unstable, and pinging my base router shows that there is a lot of erratic ping times between my satellit...
I am not entirely certain there is a problem.
Could you please explain how the device measuring ping time is attached?
Ping latency can vary a lot.
For example, I have a Windows computer connected with ethernet cable to my RBR50.
Ping times are typically 1ms.
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<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Pinging my RBS50 satellite is not as quick:
Pinging 192.168.1.5 with 32 bytes of data
Reply from 192.168.1.5: bytes=32 time=3ms TTL=64
Reply from 192.168.1.5: bytes=32 time=2ms TTL=64
Reply from 192.168.1.5: bytes=32 time=8ms TTL=64
Reply from 192.168.1.5: bytes=32 time=4ms TTL=64
I also have a Linux laptop connected to the 2.4G Orbi channel (it's old, but runs Linux just fine).
Pinging the router from this WiFi connected laptop looks like this:
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=5.07 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=2.65 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=3.25 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=2.40 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=3.02 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=34.5 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=4.62 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=5.78 ms
Notice that the pings take longer on WiFi than on ethernet, and there was one that was 10 times the average!
Pinging the satellite from this WiFi connected laptop looks like this:
PING 192.168.1.5 (192.168.1.5) 56(84) bytes of data.
64 bytes from 192.168.1.5: icmp_seq=1 ttl=64 time=11.1 ms
64 bytes from 192.168.1.5: icmp_seq=2 ttl=64 time=4.68 ms
64 bytes from 192.168.1.5: icmp_seq=3 ttl=64 time=6.50 ms
64 bytes from 192.168.1.5: icmp_seq=4 ttl=64 time=7.61 ms
64 bytes from 192.168.1.5: icmp_seq=5 ttl=64 time=9.41 ms
64 bytes from 192.168.1.5: icmp_seq=6 ttl=64 time=5.18 ms
64 bytes from 192.168.1.5: icmp_seq=7 ttl=64 time=10.8 ms
64 bytes from 192.168.1.5: icmp_seq=8 ttl=64 time=5.38 ms
Again, uniformly longer than the ethernet and longer than directly to the router.
thanks for the response! yeah i'm pinging from my desktop which is connected to a satellite which is connected wirelessly to the base router (roughly 30 feet in between).
What's weird is that during the day, this ping issue is nonexistent, the ping is always low and around 10ms. Only during the evening/night does it have these random spikes. At its worst, the average was 200ms and the spikes were up to ~600ms every 5 pings or so. This didn't happen before the update to 2.5.1.8, but it also wasn't quarantine before I updated, so I can't tell if it is one or the other. However, during the day when the ping is not quite as bad, the number of deviced using the network is not substantially higher. Could people using their networks around me be that detrimental to my backhaul connection?