NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR850 bad ping
Hello I just got an RBR850 with one router and one satellite. The bandwidth is far more better than the previous TP-Link I got except for the ping time. RBR850 router is at the same place th...
pnicolas wrote:
The bandwidth is far more better than the previous TP-Link I got except for the ping time.
RBR850 router is at the same place than the TP-Link and with the TP-Link I got a 2ms ping no matter where I test in the flat.
With RBR850 it is a 15ms ping !
It would be helpful to know what model of TP-Link was replaced by the Orbi 850.
Was it a single WiFi router, and all devices were connected to it?
Or, was it a 'mesh' system with some devices connected to the base and some to the other unit?
Thanks
yes indeed.
It was a simple router with all device connected on it, an AX3000 or Archer AX55.
RBR852 is very good, if I found how to correct the ping issue and how to change the 5 GHz channel to 52 where no neighbor is, it would be perfect !
New tests, ping RBR850 from wireless :
ping 192.168.1.72
PING 192.168.1.72 (192.168.1.72): 56 data bytes
64 bytes from 192.168.1.72: icmp_seq=0 ttl=64 time=7.126 ms
64 bytes from 192.168.1.72: icmp_seq=1 ttl=64 time=2.425 ms
64 bytes from 192.168.1.72: icmp_seq=2 ttl=64 time=3.691 ms
64 bytes from 192.168.1.72: icmp_seq=3 ttl=64 time=13.994 ms
64 bytes from 192.168.1.72: icmp_seq=4 ttl=64 time=58.139 ms
64 bytes from 192.168.1.72: icmp_seq=5 ttl=64 time=129.974 ms
64 bytes from 192.168.1.72: icmp_seq=6 ttl=64 time=153.168 ms
64 bytes from 192.168.1.72: icmp_seq=7 ttl=64 time=200.059 ms
ping RBS from wireless in the same room :
ping 192.168.1.73
PING 192.168.1.73 (192.168.1.73): 56 data bytes
64 bytes from 192.168.1.73: icmp_seq=0 ttl=64 time=192.953 ms
64 bytes from 192.168.1.73: icmp_seq=1 ttl=64 time=255.161 ms
64 bytes from 192.168.1.73: icmp_seq=2 ttl=64 time=49.416 ms
64 bytes from 192.168.1.73: icmp_seq=3 ttl=64 time=1.275 ms
64 bytes from 192.168.1.73: icmp_seq=4 ttl=64 time=265.285 ms
64 bytes from 192.168.1.73: icmp_seq=5 ttl=64 time=186.767 ms
64 bytes from 192.168.1.73: icmp_seq=6 ttl=64 time=2.328 ms
64 bytes from 192.168.1.73: icmp_seq=7 ttl=64 time=1.125 ms
very weird...
pnicolas wrote:
RBR852 is very good, if I found how to correct the ping issue and how to change the 5 GHz channel to 52 where no neighbor is, it would be perfect !
Ping on a system that uses two access points (router & satellite) will never be as fast as ping on a single access point.
That said, these results appear to give the impression of a LOT of WiFi interference.
On the second point, this cannot be done . Depending on country, Orbis are set to specific 5G WiFi channels (one 80Mhz frequency band for user devices and a separate 80Mhz band for backhaul). This is not a setting that the user can change.
This may be a result of the way the FCC regulates different frequencies.
Channel 52, for example, is one of the frequencies called DFS/TCP in the United States and Canada. See:
https://en.wikipedia.org/wiki/List_of_WLAN_channels#cite_note-N5001000-48
>>Ping on a system that uses two access points (router & satellite) will never be as fast as ping on a single access point.
Didn't know that, I will search why
Too bad for channel 52 which is allowed in France
Former Apple Airport Wifi allow to choose DFS and stick to canal 52 when there is somebody else from 36 to 48...
TP-Link router also allowed to choose 52