NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New Online Update 4.6.3.16 (RBR850/RBS850)
Just did a downgrade from 4.6.3.9 to 3.2.18.1, factory resetted and I see Netgear are pushing an update automatically to 4.6.3.16. (see attached screenshot)
This firmware is not available as an official manual update as the latest one on their downloads page is 4.6.3.9.
Has anyone updated to this firmware yet? Is it a different firmware to the beta firmware 4.6.3.16?
FURRYe38 wrote:v3.2.11.2 was last version with telnet in the debug.htm UI.
jayeshm wrote:Thanks.
I will throw it up in my guest room and see how it holds up for a few days.
Just for checking, if one has to stick with a 3.xx firmware which one do you personally recommend?
Firstly thanks for all the help furry. You have been patiently helping everyone here, and while i was being sarcastic earlier, your help is much appreciated.
Using PFsense i threw up on an old nuc, i was able to block all updates and manually shift to 3.2.18xx which is the last v3 update. So far it seems to work. Taking your advice i reset them entirely, kept them off for half a day, and then plugged them back in and added them back. I think one of my satellites is a bit wonky, since it oddly loses connection once in a while, but the rest of them seem to be holding up fine.
I have been able to successfully block updates via pfsense, since whenever i check via firmware updates manually, it gives a connection error. I looked up all the names suggested here in the various threads and added all of them to a small blocklist.
189 Replies
Had issues with the satellite after the update.
It looks like it did not manage to sync correctly post update.
Tried removing and resetting the satellite, even tried rolling back to v3 which did not last very long since I couldn't block it from updating again - using it in router mode, couldnt telnet in (no option in the debug menu anymore, putty gives me a connection refused error), blocking the update sites in the setting does not do anything really.
Being sick of looking of solutions to try get the downgrade to stick, I tried getting the new firmware to work for me via the usual power cycle + factory reset + sync
At one point, somehow the sync ended up wonky and the wireless password did not manage to get synced - I had to use the password to the default SSID to log into my network.
Kept trying and somehow it finally managed to get going by manually syncing it while having the units side by side sans cable connection to the satellite.
Plugging in the LAN cable to the satellite somehow screwed something up for me.
Even after it synced, once I plugged the cable in, the ip address resolution stopped working.
Keeping it wireless at the moment, though backhaul status remains as poor on the web console despite the satellite itself showing a solid blue when it connected (yes it shows that its a 5G connection).
I'm gonna try plugging in the cable again later when no one else is using the internet, hopefully its just my impatience that the wired connection does not work
I still wish netgear just lets consumers disable the auto update esp when most have to work from home now, any disruption to the internet is so painful.
Its rubbish for such an expensive system to be so limited and disruptive.
Safe to say I doubt I would ever opt for another netgear wifi system while this policy remains unchanged (waiting on more wifi 6e products before a switch but if such issues continue, I might just be forced to jump the gun).
Try downgrading back to v3 on the RBS first then RBR lastly then follow the link to block using telnet:
https://community.netgear.com/t5/Orbi-WiFi-6/RBK750-Series-Firmware-Update-v4-6-3-7/m-p/2130584#M18586
https://community.netgear.com/t5/Orbi-AX/RBK750-Series-Firmware-Update-v4-6-3-7/m-p/2131307/highlight/true#M18670
frostyfly wrote:
Had issues with the satellite after the update.
It looks like it did not manage to sync correctly post update.
Tried removing and resetting the satellite, even tried rolling back to v3 which did not last very long since I couldn't block it from updating again - using it in router mode, couldnt telnet in (no option in the debug menu anymore, putty gives me a connection refused error), blocking the update sites in the setting does not do anything really.
Being sick of looking of solutions to try get the downgrade to stick, I tried getting the new firmware to work for me via the usual power cycle + factory reset + sync
At one point, somehow the sync ended up wonky and the wireless password did not manage to get synced - I had to use the password to the default SSID to log into my network.
Kept trying and somehow it finally managed to get going by manually syncing it while having the units side by side sans cable connection to the satellite.
Plugging in the LAN cable to the satellite somehow screwed something up for me.
Even after it synced, once I plugged the cable in, the ip address resolution stopped working.
Keeping it wireless at the moment, though backhaul status remains as poor on the web console despite the satellite itself showing a solid blue when it connected (yes it shows that its a 5G connection).
I'm gonna try plugging in the cable again later when no one else is using the internet, hopefully its just my impatience that the wired connection does not work
I still wish netgear just lets consumers disable the auto update esp when most have to work from home now, any disruption to the internet is so painful.
Its rubbish for such an expensive system to be so limited and disruptive.
Safe to say I doubt I would ever opt for another netgear wifi system while this policy remains unchanged (waiting on more wifi 6e products before a switch but if such issues continue, I might just be forced to jump the gun).
FURRYe38 wrote:Try downgrading back to v3 on the RBS first then RBR lastly then follow the link to block using telnet:
My system auto updated again. I downgrading back to v3.2.18.233, but I have no way to telnet in to the system. The telnet option doesn't exist on the debug page. Unhiding the enable tenet option using dev tools doesn't seem to help either. Enable the option doesn't do anything.
Is there any other way to enable telnet?
Well, the autoupdate got me too, however all is still functional for me. Oddly, it didn't get my satellites and the Online Update is still offering a really old firmware (which is a downgrade from where I'm at). Everything was on v4.6.3.9 -- now my router is on v4.6.3.16, while my satellites are being offered v3.2.16.6. I won't click the update all, but I'm hoping that the system doesn't go ahead and try it (which will likely cause me all kinds of grief). Screenshot attached.
And system is working as is?
Quaksyx wrote:
Well, the autoupdate got me too, however all is still functional for me. Oddly, it didn't get my satellites and the Online Update is still offering a really old firmware (which is a downgrade from where I'm at). Everything was on v4.6.3.9 -- now my router is on v4.6.3.16, while my satellites are being offered v3.2.16.6. I won't click the update all, but I'm hoping that the system doesn't go ahead and try it (which will likely cause me all kinds of grief). Screenshot attached.
- It is — no issues actually. Part of me feels like I should update the satellites to v4.6.3.16 manually just to avoid possibility of auto update to an old firmware, but messages on here as well as a recent RMA need due to these firmware offerings have me thinking twice…
New thing for me today - checked the status of my system - now the satellite is out of sync. I rebooted it, showed a poor status. Then - back to out of sync.
What a joy.
Furry - not initerested in what you have to say about this - any reply will be ignored as this is 100% related to the firmware update failure of Netgear. No I'm not going to go down to 3.x firmware and finegeling the router(s) to prevent auto updates at this time. Netgear needs to step up.
Anyone thinking of a class action? I am.
You'll need to contact NG support this and let them know what your experiencing then.
Good Luck.
N3tworkDud3 wrote:
New thing for me today - checked the status of my system - now the satellite is out of sync. I rebooted it, showed a poor status. Then - back to out of sync.
What a joy.
Furry - not initerested in what you have to say about this - any reply will be ignored as this is 100% related to the firmware update failure of Netgear. No I'm not going to go down to 3.x firmware and finegeling the router(s) to prevent auto updates at this time. Netgear needs to step up.
Anyone thinking of a class action? I am.
Furry...your suggestion to power down everything for 24 hours seems to have remedied the satellite backhaul oscillating between poor and good that I was experiencing introduced with the 4.6.3.16 fiirmware. It has been 72 hours since power back up and I haven't seen this condition return. Thanks.
Did something interesting. Ran the Enable LAN/WAN Packet Capture on my satellite (ip.addr/debug.htm). Saw manhy calls to http://schemas.xmlsoap.org/soap/encoding/. Also saw:
- Number of hops: 255 (should be 1) With 255, the connection shows "poor"
- Many repeats for a MAC address not resolving to IP.
- Checks for Firmware in the folder for 4.6.3
- Firmware looking to https://http.fw.updates1.netgear.com/rbs850/V4.6.3/us/fileinfo.txt
- Uplink snr = 31 Rate to CAP = 520 Mbps (this one is interesting - the SNR is really low - the cap of 520 Mbps - not sure what radio it's tied to. I've suspected the Orbi has limited the speed I can get per device since installing them)
- Lots of kern.err llines
- Etc. etc etc.
Didn't run the capture that long either. Lots of interesting info. that's going to take a while to get through.
Is this with the RBS in same room as RBR or at the remote RBS location placement?
FURRYe38 wrote:Is this with the RBS in same room as RBR or at the remote RBS location placement?
If you are asking me - it's a few rooms away - don't want them too close and I'm not moving it to troubelshoot - worked great when i first bought them. Firmware updates the past year has made some functionality problematic - but not the connection between the RBR and RBS.
After update this firmware, the backhaul of satellite to Router always keeps in 2.4G, so it igives slow connection to other devices connected.
Has a factory reset and setup from scratch been performed since last FW update?
Try unpluggging the RBR and RBS for 1 hour or maybe over night when you go to bed then back ON in the morning.
So the autoupdate had hit one of my satellites [RBS850] now too (previously had updated only my router [RBR850]). My other satellite was knocked offline, which I assume was related to the autoupdate trying to push to it too. Nonetheless, I went ahead and updated the final satellite to 4.6.3.16, uneventfully (thank god). Everything was working...
I decided to go for bust and try to enable the Ethernet Port Aggregation setting again, which I reported being unsuccessful with following my previous update to the v4.x.x.x firmware series (but was running successfully prior to v4.x.x.x). FURRYe38 had reported diffiicultly as well here with the same but was able to finally get connectivity following release/renew of the router's IP a few times.
Unfortunately, I was not so lucky. Once I enabled the Ethernet Port Aggregation on my modem, made the extra connection between modem and Orbi router with another ethernet cable, and enable the setting on the Orbi, it lost internet connectivity and could not pull an IP address. I attempted to release/renew the Orbi over the next 5-10 minutes to no avail. Turning off the Ethernet Port Aggregation setting did not restore my connectivity. I could not access the config setting of my modem to turn it back off there either. I finally had to factory reset my cable modem (via paper clip), directly connect my PC to it and reactivate it onto the Comcast network, then factory reset my Orbi and set it all up again to re-establish connectivity. This was a bit painful to say the least...
I'm back up again, everything is working, but I'm not able to use Ethernet Port Aggregation anymore. Allegedly my downstream link from Comcast is 1.2 Gbps, but w/o that feature, I'm only able to realize 1 Gbps. Guess it's not that big of a deal, but it would be nice if Netgear would rectify this issue.
Be sure to contact NG support and let them know about this.
Quaksyx wrote:
So the autoupdate had hit one of my satellites [RBS850] now too (previously had updated only my router [RBR850]). My other satellite was knocked offline, which I assume was related to the autoupdate trying to push to it too. Nonetheless, I went ahead and updated the final satellite to 4.6.3.16, uneventfully (thank god). Everything was working...
I decided to go for bust and try to enable the Ethernet Port Aggregation setting again, which I reported being unsuccessful with following my previous update to the v4.x.x.x firmware series (but was running successfully prior to v4.x.x.x). FURRYe38 had reported diffiicultly as well here with the same but was able to finally get connectivity following release/renew of the router's IP a few times.
Unfortunately, I was not so lucky. Once I enabled the Ethernet Port Aggregation on my modem, made the extra connection between modem and Orbi router with another ethernet cable, and enable the setting on the Orbi, it lost internet connectivity and could not pull an IP address. I attempted to release/renew the Orbi over the next 5-10 minutes to no avail. Turning off the Ethernet Port Aggregation setting did not restore my connectivity. I could not access the config setting of my modem to turn it back off there either. I finally had to factory reset my cable modem (via paper clip), directly connect my PC to it and reactivate it onto the Comcast network, then factory reset my Orbi and set it all up again to re-establish connectivity. This was a bit painful to say the least...
I'm back up again, everything is working, but I'm not able to use Ethernet Port Aggregation anymore. Allegedly my downstream link from Comcast is 1.2 Gbps, but w/o that feature, I'm only able to realize 1 Gbps. Guess it's not that big of a deal, but it would be nice if Netgear would rectify this issue.
Quaksyx wrote:So the autoupdate had hit one of my satellites [RBS850] now too (previously had updated only my router [RBR850]). My other satellite was knocked offline, which I assume was related to the autoupdate trying to push to it too. Nonetheless, I went ahead and updated the final satellite to 4.6.3.16, uneventfully (thank god). Everything was working...
I decided to go for bust and try to enable the Ethernet Port Aggregation setting again, which I reported being unsuccessful with following my previous update to the v4.x.x.x firmware series (but was running successfully prior to v4.x.x.x). FURRYe38 had reported diffiicultly as well here with the same but was able to finally get connectivity following release/renew of the router's IP a few times.
Unfortunately, I was not so lucky. Once I enabled the Ethernet Port Aggregation on my modem, made the extra connection between modem and Orbi router with another ethernet cable, and enable the setting on the Orbi, it lost internet connectivity and could not pull an IP address. I attempted to release/renew the Orbi over the next 5-10 minutes to no avail. Turning off the Ethernet Port Aggregation setting did not restore my connectivity. I could not access the config setting of my modem to turn it back off there either. I finally had to factory reset my cable modem (via paper clip), directly connect my PC to it and reactivate it onto the Comcast network, then factory reset my Orbi and set it all up again to re-establish connectivity. This was a bit painful to say the least...
I'm back up again, everything is working, but I'm not able to use Ethernet Port Aggregation anymore. Allegedly my downstream link from Comcast is 1.2 Gbps, but w/o that feature, I'm only able to realize 1 Gbps. Guess it's not that big of a deal, but it would be nice if Netgear would rectify this issue.
I had initial issues with Port Aggregation as well, but this seems normal for me...what I did was unplug the 2nd cable and get things running without Aggregation, and then once all was stable, I plugged the cable back in and enabled it and rebooted everything. This has been typical since day one with the 850, but it does finally work.
Disappointed....this seems like Beta Software. I skipped the 4.6.3.9 upgrade due to all the negative comments and it looked like everything was fixed version 16. First, only of my wired satelites appeared in the network map. I readded the satelite successfully using the wireless backhaul, then plugged in the wire for the backhaul. The network map (router & 2 wired satellites) was displaying correctly on the apple mobile app, but it only shows the one satellite the windows web version. Oddly, the second satellite shows up as a connected device when you click on the connected device tile. Also, the speed test feature does not work in either the web version or apple app. From what I can tell, the router and satellites are working properly, but I wouldn't know that by looking at app/web interface page. Netgear really needs to up their QC on the firmware....I expect better for what they are charging for this system! (RBK853, wired backhaul in AP mode, 1GB Fios)
I downgrade my system to v18 couple of weeks ago. Wanted to see if it worked. It worked. Also system worked on AP mode as of yesterday;
After I was finished checking AP mode with RBS ethernet conencted on v3 yesterday, I figured lets see what happens if I let the system update back to v4/16. I used the RBRs FW update web page check for FW updates and v16 was seen for all. I selected the UPDATE ALL button and let'r rip. I saw the RBS start to blink WHITE and the RBR finally started blinking WHITE. The RBS came back online and showed BLUE. RBR pulsated WHITE then turned OFF. I powered OFF the RBS and RBR for a couple of minutes, then back on with the RBR first then RBS lastly. RBS turned BLUE then eventually turned OFF. RBR still in AP mode and RBS ethernet connected to the RBR via HP ProCurve 1400 series LAN switch.
tjtrimble wrote:Disappointed....this seems like Beta Software. I skipped the 4.6.3.9 upgrade due to all the negative comments and it looked like everything was fixed version 16. First, only of my wired satelites appeared in the network map. I readded the satelite successfully using the wireless backhaul, then plugged in the wire for the backhaul. The network map (router & 2 wired satellites) was displaying correctly on the apple mobile app, but it only shows the one satellite the windows web version. Oddly, the second satellite shows up as a connected device when you click on the connected device tile. Also, the speed test feature does not work in either the web version or apple app. From what I can tell, the router and satellites are working properly, but I wouldn't know that by looking at app/web interface page. Netgear really needs to up their QC on the firmware....I expect better for what they are charging for this system! (RBK853, wired backhaul in AP mode, 1GB Fios)
I skipped 4.6.3.9 as well as it was so short-lived I never had the time to do it. But this version seems solid and I did a "dirty upgrade" - no reset, just manual install, power off for 30 minutes or so while I was working on something else, then it booted up fine other than the Wan Aggregation which always takes a bit to get set up. I cannot comment on the 2nd BRS as I only have one and it is wired, but everything else seems fine and the Speedtest and other features seem OK both from the Browser or iPhone app.
So crazy how we all see quite different and odd issues. I did have Speedtest issues yesterday, but I think that may have been related to WEB outages: Facebook, Xfinity Mobile, and Ookla at least for me didn't work most of the day.
{deleted}
Well were hoping that with the newer 7 series FW, that NG will be publishing same for the 8 series. Give it some time though as Im sure NG wants to see results of 7 series experiences before sending out 8 series. :smileywink:
Any word on the 4.6.5.x "upgrade" for the 8 series? All my devices appear to functioning properly, however the UI is still a complete mess (inconsistent between web/app, missing satellite, devices showing as wired when they are wireless, speed test inop) This firmware fiasco really inspires me to upgrade to the new 6E version of the Orbi for $1500....NOT.
NG doesn't let us know when new FW is forth coming. Have to keep an eye on NGs download site or here in the forums.
You might try this users process:
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
tjtrimble wrote:This firmware fiasco really inspires me to upgrade to the new 6E version of the Orbi for $1500....NOT.
OMG - I thought you were insane until I saw the NOT. ASUS - I'm considering going with their AI-Mesh stuff.
N3tworkDud3 wrote:OMG - I thought you were insane until I saw the NOT. ASUS - I'm considering going with their AI-Mesh stuff.
My previous AI-Mesh configuration was much more reliable. I've had to take my service provider's modem out of gateway mode, so I could use it in front of the Orbi to block the update servers. That's letting me stay on the V3 firmware until they fix things.
I'm considering either going back to an Asus config or move to Ubiquiti.
