Forum Discussion

Guru

Sep 17, 2021

New RBR850 / RBS850 Firmware Version 4.6.3.16 Released

Security Fixes: Fixes security vulnerabilities. For more information about security vulnerabilities, visit https://www.netgear.com/about/security. Bug Fixes: Fixes the issue where the s...

gthi

Guide

Oct 11, 2021

This is what happens when you ping rhe router during drop outs.

The wifi connection is maintained (coverage is ok) nut the router time outs and responds at the same time

Firmware Version
V4.6.3.16_2.0.51

This is definitely a routing problem (firmware related) and has nothing to do with coverage.

I will return the whole 1800 euro system in te next couple of days for a refund.

Good bye Netgear

Last login: Fri Oct 8 15:57:16 on console
MacBook ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=2390.607 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=1882.943 ms
64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=911.565 ms
64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=247.726 ms
64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=164.955 ms
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
64 bytes from 10.0.0.1: icmp_seq=6 ttl=64 time=4442.170 ms
64 bytes from 10.0.0.1: icmp_seq=7 ttl=64 time=3592.775 ms
64 bytes from 10.0.0.1: icmp_seq=8 ttl=64 time=2659.576 ms
64 bytes from 10.0.0.1: icmp_seq=9 ttl=64 time=1758.673 ms
64 bytes from 10.0.0.1: icmp_seq=11 ttl=64 time=446.292 ms
64 bytes from 10.0.0.1: icmp_seq=13 ttl=64 time=189.283 ms
64 bytes from 10.0.0.1: icmp_seq=14 ttl=64 time=206.045 ms
64 bytes from 10.0.0.1: icmp_seq=15 ttl=64 time=586.657 ms
64 bytes from 10.0.0.1: icmp_seq=17 ttl=64 time=879.643 ms
64 bytes from 10.0.0.1: icmp_seq=18 ttl=64 time=1997.987 ms
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
64 bytes from 10.0.0.1: icmp_seq=19 ttl=64 time=3749.005 ms
64 bytes from 10.0.0.1: icmp_seq=20 ttl=64 time=2903.914 ms
64 bytes from 10.0.0.1: icmp_seq=21 ttl=64 time=2062.794 ms
64 bytes from 10.0.0.1: icmp_seq=22 ttl=64 time=1072.782 ms
64 bytes from 10.0.0.1: icmp_seq=24 ttl=64 time=353.735 ms
64 bytes from 10.0.0.1: icmp_seq=25 ttl=64 time=256.697 ms
64 bytes from 10.0.0.1: icmp_seq=28 ttl=64 time=119.776 ms
Request timeout for icmp_seq 29
64 bytes from 10.0.0.1: icmp_seq=30 ttl=64 time=284.688 ms
Request timeout for icmp_seq 31
Request timeout for icmp_seq 32
Request timeout for icmp_seq 33
Request timeout for icmp_seq 34
Request timeout for icmp_seq 35
64 bytes from 10.0.0.1: icmp_seq=33 ttl=64 time=3801.090 ms
64 bytes from 10.0.0.1: icmp_seq=34 ttl=64 time=2798.878 ms
64 bytes from 10.0.0.1: icmp_seq=35 ttl=64 time=1981.872 ms
64 bytes from 10.0.0.1: icmp_seq=36 ttl=64 time=994.666 ms
Request timeout for icmp_seq 40
Request timeout for icmp_seq 41
Request timeout for icmp_seq 42
Request timeout for icmp_seq 43
64 bytes from 10.0.0.1: icmp_seq=41 ttl=64 time=3597.974 ms
64 bytes from 10.0.0.1: icmp_seq=42 ttl=64 time=2926.867 ms
64 bytes from 10.0.0.1: icmp_seq=43 ttl=64 time=1972.007 ms
Request timeout for icmp_seq 47
Request timeout for icmp_seq 48
64 bytes from 10.0.0.1: icmp_seq=49 ttl=64 time=70.251 ms
Request timeout for icmp_seq 50
64 bytes from 10.0.0.1: icmp_seq=50 ttl=64 time=1234.359 ms
64 bytes from 10.0.0.1: icmp_seq=52 ttl=64 time=343.502 ms
64 bytes from 10.0.0.1: icmp_seq=53 ttl=64 time=5.607 ms
64 bytes from 10.0.0.1: icmp_seq=54 ttl=64 time=250.506 ms
64 bytes from 10.0.0.1: icmp_seq=55 ttl=64 time=10.574 ms
64 bytes from 10.0.0.1: icmp_seq=56 ttl=64 time=46.056 ms
64 bytes from 10.0.0.1: icmp_seq=57 ttl=64 time=36.372 ms
64 bytes from 10.0.0.1: icmp_seq=58 ttl=64 time=77.407 ms
64 bytes from 10.0.0.1: icmp_seq=59 ttl=64 time=106.047 ms
Request timeout for icmp_seq 60
Request timeout for icmp_seq 61
Request timeout for icmp_seq 62

RBR853+ 4X RBS850

p0se1d0nX

Star

Oct 12, 2021

Maybe I’m just lucky but my RBK852 has not hiccuped once since this fw update. I did factory reset after the latest update and set up it again from scratch (didn’t use a backup settings file) so I’m not sure if that’s a reason why but I haven’t had any slowdown/disconnects/drop-offs or any other issues with this update that many others are experiencing.
¯\_(ツ)_/¯

ChrisBoer
Guide
Nov 30, 2021
Do you use your ORBI as AP or as ROUTER because once I started using it as ROUTER the problems started.
- FURRYe38
  Guru
  Nov 30, 2021
  It was reported the AP mode helped alleviate problems seen in router mode.
  
  You may need to factory reset the system and power the system OFF as well.
  https://community.netgear.com/t5/Orbi-WiFi-6-AX-and-WiFi-6E-AXE/New-RBR850-RBS850-Firmware-Version-4-6-3-16-Released/m-p/2150287/highlight/true#M21560
  https://community.netgear.com/t5/Orbi-WiFi-6-AX-and-WiFi-6E-AXE/New-RBR850-RBS850-Firmware-Version-4-6-3-16-Released/m-p/2150391/highlight/true#M21575
  https://community.netgear.com/t5/Orbi-WiFi-6-AX-and-WiFi-6E-AXE/New-RBR850-RBS850-Firmware-Version-4-6-3-16-Released/m-p/2150417/highlight/true#M21579
  
  What I did to get v4.6.3.16 working on 8 series in router mode:
  https://community.netgear.com/t5/Orbi-WiFi-6-AX-and-WiFi-6E-AXE/New-Online-Update-4-6-3-16-RBR850-RBS850/m-p/2155645/highlight/true#M22357
  https://community.netgear.com/t5/Orbi-WiFi-6-AX-and-WiFi-6E-AXE/New-Online-Update-4-6-3-16-RBR850-RBS850/m-p/2154700/highlight/true#M22256
  
  ChrisBoer wrote:
  
  Do you use your ORBI as AP or as ROUTER because once I started using it as ROUTER the problems started.
  - izme
    Star
    Nov 30, 2021
    I am using for my LAN setup another ip-range than the usual (like xx.xx.xx.xx for router IP, Address with IP Subnet Mask 255.255.255.0), however I see some devices attached with Ip numbers in the normal range (192.168.2.0 etc) which is outside the range I am using. Shouldn't that not be possible at all?
    
    Still strugling btw with fall-outs. I am now trying with the wireless sattelite (which often had backhaul status poor) moved to a place where it can be wired (now both my sattelites are backhaul wired with status good
FURRYe38
Guru
Oct 12, 2021
Glad it's working for you as well.

How was yours updated? Auto Update, thru the RBRs web page or manually install FW files using a PC and web browser?

Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/000062080/How-do-I-back-up-the-configuration-settings-on-my-Orbi-WiFi-System
Enjoy.

p0se1d0nX wrote:
Maybe I’m just lucky but my RBK852 has not hiccuped once since this fw update. I did factory reset after the latest update and set up it again from scratch (didn’t use a backup settings file) so I’m not sure if that’s a reason why but I haven’t had any slowdown/disconnects/drop-offs or any other issues with this update that many others are experiencing.
¯\_(ツ)_/¯
- p0se1d0nX
  Star
  Oct 12, 2021
  I updated via the Orbi app then I performed a factory reset via the web login gui followed by a hard reboot of my Orbi router and satellite.
  
  I proceeded to set up everything from scratch (I took pictures of my previous settings for quick reference and used the same SSID and PW so all my devices connected again).
  
  Upon fw update completion I hard booted the router and satellite once again (in that order - making sure the router powers up first followed by powering up any satellites).
  
  I’ve done this since the first day the new firmware update was available and I haven’t had any of these issues that many others have reported (knock on wood). Literally not even one!
  - FURRYe38
    Guru
    Oct 12, 2021
    This "hard boot" is this a power OFF of the RBR and RBS? Is, for how long?
    
    p0se1d0nX wrote:
    I updated via the Orbi app then I performed a factory reset via the web login gui followed by a hard reboot of my Orbi router and satellite.
    
    I proceeded to set up everything from scratch (I took pictures of my previous settings for quick reference and used the same SSID and PW so all my devices connected again).
    
    Upon fw update completion I hard booted the router and satellite once again (in that order - making sure the router powers up first followed by powering up any satellites).
    
    I’ve done this since the first day the new firmware update was available and I haven’t had any of these issues that many others have reported (knock on wood). Literally not even one!