NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
esiebert7625
Oct 04, 2018Star
Your experience with Firmware 2.2.1.210 released as of 10/3/18
The other long thread on the new firmware is useless and has become a tech support thread. Please only post your experience after upgrading to the new firmware, good or bad. I'd like to see everyone'...
Daniel_K
Oct 31, 2018Aspirant
I'm an IT consultant. I installed the RBK50 system over one year ago for a client. My client's video streaming became largely unusable around the time of the .210 release. I visited my client a few days ago. The wireless backhaul was "poor." I restarted the satellite and streaming worked fine again. By the evening, the problems started up again. After the satellite was unplugged, streaming worked fine again.
I noticed that after restarting the satellite, the ring turned magenta before it turned blue. I never recall it doing that before the .210 release.
- ekhalilOct 31, 2018Master
Daniel_K wrote:
I'm an IT consultant. I installed the RBK50 system over one year ago for a client. My client's video streaming became largely unusable around the time of the .210 release. I visited my client a few days ago. The wireless backhaul was "poor." I restarted the satellite and streaming worked fine again. By the evening, the problems started up again. After the satellite was unplugged, streaming worked fine again.
I noticed that after restarting the satellite, the ring turned magenta before it turned blue. I never recall it doing that before the .210 release.
This software seems to have issues with some wired devices. If you have any mesh speakers (e.g. Sonos) wired to Orbi, please test to disconnect them and see if you will see improvements.
Wired Sonos seem to cause IP loops over time which will degrade the system performance and will consequently cause different "strange" issues.
- ratb3rtOct 31, 2018Tutor
I have used the instructions on post 105 on the link below to stop auto updating. Well, for the last 5 days anyway. Before when I rolled back the firmware, it auto updated immediately after connecting to the cable modem.
There are a couple of things to mention. There is a line orbi_auto_upg=0 in the OP. In my router it was set to =1. I didn't notice it at first, and my router updated even after setting the other lines to =0. I found another post that mentioned this, so be sure to set this like the others to =0 if it is not already. Also the line orbi_auto_upgrade may have a value greater than 1 when you start. Just set it to =0. Thirdly the OP says in step 6 not to put a space after "set". That did not work for me. I put a space in and the command worked.
Now when I log into the router I see a notice that there is new firmware, but it does not auto update. Hooray! My Carrier Infinity Touch thermostats are connecting again and I don't need an additional AP!
https://community.netgear.com/t5/Orbi/Firmware-V1-12-0-18-Discussion/td-p/1320421/page/5