NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Layla38
Mar 03, 2021Tutor
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....
Layla38
Mar 04, 2021Tutor
It seems the working satellite connects to the router and the one with issues connects through the working one. Internet - > router - > good box - > my box
I have measured the spikes:
Reply from 8.8.8.8: bytes=32 time=498ms TTL=113
Reply from 8.8.8.8: bytes=32 time=34ms TTL=113
Reply from 8.8.8.8: bytes=32 time=491ms TTL=113
Reply from 8.8.8.8: bytes=32 time=34ms TTL=113
FURRYe38
Mar 04, 2021Guru - Experienced User
How are you connexcted to the system? At the RBR or RBS?
What is the distance between the router and satellite(s)? 30 feet or more is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected.
What wireless device are you using to test with?
Are you pinging the RBS IP address?
What Firmware version is currently loaded?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Try using PingPlotter.com with a wired PC connected to the ISP Modem first, then with the RBR inline.
- Layla38Mar 04, 2021Tutor
I am connected through the RBS.
I'd say the distance between satellite and router is about 15m with the good satellite being on the same level and the bad satellite being a floor below.
I use a wired computer to test. When I use a wireless device I turn off the bad satellite and I will connect to the good one and have no problems.
I don't think Im pinging the RBS servers, how do I do/check?
Firmware version 2.5.2.4
I don't want to leak my ISP unless this is vital information- FURRYe38Mar 04, 2021Guru - Experienced User
Try swapping RBS with each other to see if problems follows?
v4 out of date FW as there is newer version available:
Giving the modem brand and model# doesn't reveal ISP info. However we are looking to see if there is additional features like a router and wifi here as these can cause problems is the only reason for asking. ISP information given doesn't matter, only for troubleshooting information only.My ping results:64 bytes from 192.168.0.150: icmp_seq=17 ttl=64 time=10.444 ms
64 bytes from 192.168.0.150: icmp_seq=18 ttl=64 time=10.243 ms
64 bytes from 192.168.0.150: icmp_seq=19 ttl=64 time=10.999 ms
64 bytes from 192.168.0.150: icmp_seq=20 ttl=64 time=5.092 ms
64 bytes from 192.168.0.150: icmp_seq=21 ttl=64 time=9.928 ms
64 bytes from 192.168.0.150: icmp_seq=22 ttl=64 time=11.325 ms
64 bytes from 192.168.0.150: icmp_seq=23 ttl=64 time=10.049 ms
64 bytes from 192.168.0.150: icmp_seq=24 ttl=64 time=10.507 ms
64 bytes from 192.168.0.150: icmp_seq=25 ttl=64 time=11.609 ms
64 bytes from 192.168.0.150: icmp_seq=26 ttl=64 time=10.413 ms
64 bytes from 192.168.0.150: icmp_seq=27 ttl=64 time=11.317 ms
64 bytes from 192.168.0.150: icmp_seq=28 ttl=64 time=10.502 ms
64 bytes from 192.168.0.150: icmp_seq=29 ttl=64 time=10.937 ms
64 bytes from 192.168.0.150: icmp_seq=30 ttl=64 time=6.491 ms
64 bytes from 192.168.0.150: icmp_seq=31 ttl=64 time=10.802 ms
64 bytes from 192.168.0.150: icmp_seq=32 ttl=64 time=10.731 ms
64 bytes from 192.168.0.150: icmp_seq=33 ttl=64 time=10.758 ms
64 bytes from 192.168.0.150: icmp_seq=34 ttl=64 time=12.391 ms
64 bytes from 192.168.0.150: icmp_seq=35 ttl=64 time=12.112 ms
64 bytes from 192.168.0.150: icmp_seq=36 ttl=64 time=11.563 ms
64 bytes from 192.168.0.150: icmp_seq=37 ttl=64 time=10.858 ms
64 bytes from 192.168.0.150: icmp_seq=38 ttl=64 time=10.430 ms
64 bytes from 192.168.0.150: icmp_seq=39 ttl=64 time=10.391 ms
64 bytes from 192.168.0.150: icmp_seq=40 ttl=64 time=8.883 ms
64 bytes from 192.168.0.150: icmp_seq=41 ttl=64 time=11.016 ms
64 bytes from 192.168.0.150: icmp_seq=42 ttl=64 time=9.959 ms
64 bytes from 192.168.0.150: icmp_seq=43 ttl=64 time=10.377 ms
64 bytes from 192.168.0.150: icmp_seq=44 ttl=64 time=12.390 ms
64 bytes from 192.168.0.150: icmp_seq=45 ttl=64 time=12.310 ms- Layla38Mar 05, 2021Tutor
FURRYe38
I tried switching the satellites. The problems followed. This reply comes late as there were no problems until now.
I have also discovered that the router we use is the RBR50, the satellite with no problems is the RBS50v2, the satellite with problems is the RBS50. Could the difference in versions be causing problems?The modem is a Huawei HG659b Modem.