NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AX6000 Orbi RBK853 unstable quality and not good performance
hi guys, i have a RBK853 — Orbi WiFi 6 System AX6000 system on my home.. a RBR + 2 Satellite. The configuration is pretty easy, RBR is configured as WIFI Mode, it is connected via Gigabit LAN t...
Here with AUTO and 40
Mobile phone still no view the SSID on 2.4..
I don't see any CASCINA on 2,4.. it's really weird
So with the RBS turned OFF, lets factory reset the RBR. Press the reset button for 15 seconds then release. When you see the front LED pulsate WHITE, power off the RBR for 1 minute then back ON. Walk thru the setup wizard when you see the front LED pulsate WHITE. After the RBR is setup, check for SSID signals.
I did.. but now good news..
RBR is the only one power one.. RBS are power down.
RBR seems to not power on the 2,4 AP 😞 at all.. i configured it on chaneel 11
ping is unstable and the quality is poor
64 bytes from 192.168.111.1: icmp_seq=82 ttl=64 time=11.6 ms
64 bytes from 192.168.111.1: icmp_seq=83 ttl=64 time=51.7 ms
64 bytes from 192.168.111.1: icmp_seq=84 ttl=64 time=2.77 ms
64 bytes from 192.168.111.1: icmp_seq=85 ttl=64 time=69.8 ms
64 bytes from 192.168.111.1: icmp_seq=86 ttl=64 time=172 ms
64 bytes from 192.168.111.1: icmp_seq=87 ttl=64 time=5.19 ms
64 bytes from 192.168.111.1: icmp_seq=88 ttl=64 time=2.18 ms
64 bytes from 192.168.111.1: icmp_seq=89 ttl=64 time=2.67 ms
64 bytes from 192.168.111.1: icmp_seq=90 ttl=64 time=1.66 ms
64 bytes from 192.168.111.1: icmp_seq=91 ttl=64 time=96.2 ms
64 bytes from 192.168.111.1: icmp_seq=92 ttl=64 time=64.4 ms
64 bytes from 192.168.111.1: icmp_seq=93 ttl=64 time=98.2 ms
64 bytes from 192.168.111.1: icmp_seq=94 ttl=64 time=134 ms
64 bytes from 192.168.111.1: icmp_seq=95 ttl=64 time=4.76 ms
64 bytes from 192.168.111.1: icmp_seq=96 ttl=64 time=4.49 ms
64 bytes from 192.168.111.1: icmp_seq=97 ttl=64 time=37.1 ms
64 bytes from 192.168.111.1: icmp_seq=98 ttl=64 time=69.8 ms
64 bytes from 192.168.111.1: icmp_seq=99 ttl=64 time=103 ms
64 bytes from 192.168.111.1: icmp_seq=100 ttl=64 time=71.9 ms
64 bytes from 192.168.111.1: icmp_seq=101 ttl=64 time=169 ms
64 bytes from 192.168.111.1: icmp_seq=102 ttl=64 time=2.95 ms
64 bytes from 192.168.111.1: icmp_seq=103 ttl=64 time=2.24 ms
64 bytes from 192.168.111.1: icmp_seq=104 ttl=64 time=9.23 ms
64 bytes from 192.168.111.1: icmp_seq=105 ttl=64 time=38.6 ms
64 bytes from 192.168.111.1: icmp_seq=106 ttl=64 time=5.97 ms
64 bytes from 192.168.111.1: icmp_seq=107 ttl=64 time=41.3 ms
64 bytes from 192.168.111.1: icmp_seq=108 ttl=64 time=135 ms
64 bytes from 192.168.111.1: icmp_seq=109 ttl=64 time=5.43 ms
64 bytes from 192.168.111.1: icmp_seq=110 ttl=64 time=198 ms
64 bytes from 192.168.111.1: icmp_seq=111 ttl=64 time=7.39 ms
64 bytes from 192.168.111.1: icmp_seq=112 ttl=64 time=2.63 ms
64 bytes from 192.168.111.1: icmp_seq=113 ttl=64 time=3.52 ms
64 bytes from 192.168.111.1: icmp_seq=114 ttl=64 time=64.5 ms
64 bytes from 192.168.111.1: icmp_seq=115 ttl=64 time=95.9 ms
64 bytes from 192.168.111.1: icmp_seq=116 ttl=64 time=129 ms
64 bytes from 192.168.111.1: icmp_seq=117 ttl=64 time=5.61 ms
64 bytes from 192.168.111.1: icmp_seq=118 ttl=64 time=193 ms
64 bytes from 192.168.111.1: icmp_seq=119 ttl=64 time=2.37 ms
64 bytes from 192.168.111.1: icmp_seq=120 ttl=64 time=2.51 ms
64 bytes from 192.168.111.1: icmp_seq=121 ttl=64 time=26.2 ms
64 bytes from 192.168.111.1: icmp_seq=122 ttl=64 time=2.78 ms
64 bytes from 192.168.111.1: icmp_seq=123 ttl=64 time=89.0 ms
64 bytes from 192.168.111.1: icmp_seq=124 ttl=64 time=121 ms
64 bytes from 192.168.111.1: icmp_seq=125 ttl=64 time=1.99 ms
64 bytes from 192.168.111.1: icmp_seq=126 ttl=64 time=2.41 msYa seems bad. If this is seen across other devcies as well, I'm going to recommend that you contact NG support and ask for help and information regarding this. Ask about RMA options if available.
https://my.netgear.com/support/contact.aspx
