NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Ping spikes Orbi Satellite RBS50
In my household there are two of these RBS50v2 extenders. When connected via an ethernet cord to one of the boxes, there are no issues. When connected to the other box there are frequent ping spikes....
Hi, CrimpOn
My results came to :
Pinging 192.168.1.1 with 32 bytes of data
Reply from 192.168.1.72: Destination host unreachable.
Reply from 192.168.1.72: Destination host unreachable.
Reply from 192.168.1.72: Destination host unreachable.
Reply from 192.168.1.72: Destination host unreachable.
Is this the wrong adress? How do I find the correct one?
Also, when i switched the satellites around like furrye suggested, the network map switched to:
Internet
Router(RBR50)
Bad Satellite (RBS50) Good Satellite(RBS50v2)
Layla38 wrote:Hi, CrimpOn
My results came to :
Pinging 192.168.1.1 with 32 bytes of data
Reply from 192.168.1.72: Destination host unreachable.
The Orbi router will be the IP "gateway" for all devices connected to the Orbi. It will have the same IP address as all of the other devices except the last digit will be "1". i.e. 192.168.1.1 or 10.0.0.1.
CrimpOn
Reply from 10.0.0.1: bytes=32 time=4ms TTL=64Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=74ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=8ms TTL=64
Small variations up to 20 but a few big ones like shown
Layla38 wrote:CrimpOn
Reply from 10.0.0.1: bytes=32 time=4ms TTL=64Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=74ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=8ms TTL=64
Small variations up to 20 but a few big ones like shown
I hate to break it to you, but 74ms is .074 seconds. Less than 1/10 of a second. I know gamers are fast, but not that fast.
If pinging the router from the (bad) satellite takes less than 1/10th of a second (reliably, over a long period of time), then the issue may be external to the Orbi.
Yeah you're right Im not going to notice 0.07s. I was impatient and just recorded the first jump I saw
Here is lines from a test i just did:
Reply from 10.0.0.1: bytes=32 time=4ms TTL=64Reply from 10.0.0.1: bytes=32 time=4ms TTL=64
Reply from 10.0.0.1: bytes=32 time=536ms TTL=64
Reply from 10.0.0.1: bytes=32 time=5ms TTL=64
Reply from 10.0.0.1: bytes=32 time=5ms TTL=64
Over a minute period, there were 7 pings over 100ms with 534 being the peak.
.1 or .5 may not sound like much of a second but if these are frequent (which they can be) or are consistent, it becomes very disruptive.
Not trying to say the issue is 100% my orbi box, just making sure I have said everything