NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR850 Frequent Disconnects Starting March 9th AM EST
Yesterday 3/9, starting at about 6AM EST, my Orbi system is disconnecting my Nest Cameras and Thermostat and my work laptop every 10-20 mins or so. I have about 20 devices connected to my mesh syste...
You can't see the server :) But when you check for updates in the Orbi app or in the web GUI you will get information about the latest firmware available on the update server.
ZOOShen wrote:
Could you tell me their upgrade server address?
Actually, you can see their server. If you telnet into the router you can see the updates server by using the following command:
nvram show ver | sort
That will show you ftp and https servers. For example
ver_check_ftp_svr1=updates1.netgear.com
ver_check_ftp_svr2=updates1.netgear.com
ver_check_ftp_svr3=updates1.netgear.com :
ver_check_https_svr1=http.fw.updates1.netgear.com
So, in theory adding updates1.netgear.com to the blocked list should prevent the router from being able to pull automatic updates. I'm not 100% positive this will stop the nightly updating, but it appears to have prevented the web gui from knowing whether updates are available. You can confirm this by looking at the firmware update page. It will show service unreachable. I'm crossing my fingers that this will work, but I have to wait until midnight to know for sure.
If you use an external router, you need to enable DNS forwarding on the router and then configure Orbi to use the router as its DNS server. Then, simply tweak the hosts file on the router. You can do it manually, or if you have an EdgeRouter like me, go to the CLI and try something like that:
set system static-host-mapping host-name updates1.netgear.com inet 127.0.0.1
set system static-host-mapping host-name http.fw.updates1.netgear.com inet 127.0.0.1
Commit and save and you're done.
Note: I use Orbi as AP, not as router. I use an EdgeRouter 4 for routing. Obviously, it doesn't work if you use Orbi as router and there is nothing in the way to block the requests to Netgear.
- You could potentially set the Orbi (as router) to manually use nextdns.io as its DNS. You would have to set up an account and then put a rule in to block the Netgear hostname(s) for their update servers. This assumed Netgear haven't hard coded their update server DNS in some way.
- I should add that Netgear have "helpfully" moved the IPv6 DNS settings to the Advanced/IPv6 settings area and not in with IPv4 DNS, so if you enable IPv6, make sure to update both places.
My attempts to block the upgrade by setting "install_fw_upgrade_latest=0" in firmware failed. The upgrade to 3.2.9.2 happened anyway.
I'll try what others have suggested above to see if I can block the router's path to the upgrade servers.
Unfortunatley, I no longer have my older router, so for me using the orbi as an AP won't work, and I'm not thrilled with the idea of buy *another* router.
I recommend that you download the v3.2.9.2 FW files to a wired PC. Manually load these files on to the RBS and RBR. Then factory reset the RBS and RBR by pressing the reset button in back for 15 seconds. Power OFF the ISP modem/ONT for 30 seconds then back ON. Walk thru the setup wizard with the wired PC and web browser.
angelogouvis wrote:My attempts to block the upgrade by setting "install_fw_upgrade_latest=0" in firmware failed. The upgrade to 3.2.9.2 happened anyway.
I'll try what others have suggested above to see if I can block the router's path to the upgrade servers.
Unfortunatley, I no longer have my older router, so for me using the orbi as an AP won't work, and I'm not thrilled with the idea of buy *another* router.
Thanks for the suggestion FURRYe38 . However, I've had good luck with the v3.1.5.23_1.0.46 firmware, and I'm inclined make efforts to keep that version in place until such time that Netgear offers an updated firmware that addresses these issues.
any update on this ? i have v3.2.9.2. skype and anydesk disconnects every 10 to 15 minutes.
Ok, thanks for letting us know. Hopefully next update will correct things.
angelogouvis wrote:Thanks for the suggestion FURRYe38 . However, I've had good luck with the v3.1.5.23_1.0.46 firmware, and I'm inclined make efforts to keep that version in place until such time that Netgear offers an updated firmware that addresses these issues.
What is the Mfr and model# of the ISP modem the NG router is connected too?
Has a factory reset and setup from scratch been performed since last FW update?
Be sure to check your CTS and RTS values. If they are at 64, please change both to 2347. Reboot both RBR and wireless devices.
Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
What is the distance between the router and satellite(s)? 30 feet is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected. https://kb.netgear.com/000036466/How-far-should-I-place-my-Orbi-satellite-from-my-Orbi-router
Try disabling the following and see:
IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Set Short preamble instead of Long preamble modes.
quethrosar wrote:any update on this ? i have v3.2.9.2. skype and anydesk disconnects every 10 to 15 minutes.
So, my latest modifications to configurations in an attempt to block auto-update and hang on to known-good (at least for me) firmware version v3.1.5.23_1.0.46 is as follows:
Router and Satellite:nvram settings:
auto_upgrade_enable=0
ver_check_enable=0
Router:
blocked sites:
http.fw.updates1.netgear.com
updates1.netgear.comOn the Router via the web UI admin, in Advanced mode, for the Firmware update screen, it now (correctly) shows the Current Version of the firmware as V3.1.5.23. For the Router, for the Status column, it shows "Service Unreacheable" for the Router, and "v3.2.9.2" for the Satellite. The fact that the Satellite can see v3.2.9.2 is a bit of mystery to me, but I'm hoping because I blocked the domains for the upgrades, I'm hoping I've "crippled" the automated upgrade capabilities. I'll know for sure tomorrow morning......
v3.2.9.2 on the RBS should be a problem. ITs the RBR that has the problem. You'd be fine with the RBS where ever it ends up at.
Leave it for now and lets see what NG does for us.
