NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi firmware v2.1.1.16 discussion
do we need to do nvram wipe for this 2.1.1.16 Firmware just released today? noticed it downloaded automatically.
437 Replies
4+ days since I last rebooted. Everything stable, no issues other than the satellite/device reporting issue which the new beta apparently resolves. But I'm hesitant to try the beta since everything else is working so well!
I want to take some time to play with my setup when I have a few minutes. I'd like to unplug the ethernet cable from one or both satellites and test the wireless backhaul. If/when I do that, should the wireless backhaul immediately pickup the connection? Or will I need to powercycle the satellite and/or router?
And vice versa when I reconnect the wired connection? Do I need to do anything to force the wired/wireless connection if I switch back and forth?
When my system upgraded to 2.1.1.16, my android phone lost its ability to connect to the network. Only when I set my Secuirty Options to WPA-PSK [TKIP] + WPA2-PSK [AES] was I able to get my phone back on the network.
I would very much like to go back to the more secure approach requiring WPA2-PSK [AES] only. Since I had been working in that mode for a couple of months, I can only assume 2.1.1.16 introduced an issue.
Any ideas on what I can do, or an acknowledgement that Netgear is aware of the issue and working on it? Since I am new to netgear I would like to learn how I can report this issue to Netgear directly.
- That's very strange. My Android is running Oreo 8.0 and my router security is set to aes only. All our mobile clients from Android to iOS have no issues connecting.
It really seamed strange to me also. I am on Android 7.0 with no chance to upgrade.
The other Android phones in the house (one older, one newer) had no issues either.
In looking at my phone, I cannot find a way to change any connection security settings.
First time doing the telnet thing so I downloaded PuTTY for my Win 10 PC. According to the instructions here:
https://community.netgear.com/t5/Orbi/Firmware-V1-12-0-18-Discussion/td-p/1320421/page/5
I should be seeing a different auto_upgrade flag. Instead of a '1', I see a '0', the one it should be changed to, per the instructions.
The auto_check_for_upgrade=1 shows the same as the instructions, so I'll change that. Other than that 1 change, is there anything else that needs to be done to stop the auto upgrades that are pushed out?
Edit: now that I think about it, it appears the auto upgrade feature is now disabled by default; the system only checks for an upgrade, but won't automatically perform the upgrade.
If that's true, then I'm going to leave the settings alone as I would like to be informed of an upgrade, but only do the upgrade when I choose to do so. Do I understand this correctly?
Edit: this is for one of the satellites. I'll check the router itself and post separately.
Following the instructions from the above linked thread, I easily brought up the router config page.. which looked a lot more like the instructions! I made changes to only 2 of the command lines. The first one (orbi_auto_upgrade=x) already had a number greater than 1, so I left it alone instead of changing it to zero.
So now I expect to be notified of an upgrade, but only do a manual upgrade at my leisure instead of having the update done for me.
RBR50 telnet info
Nearly 3 days since I manually rebooted the system. I've not seen any spurious reboots or loss of connectivity since I installed the Orbi system about 10 days ago.
The minor nits have so far been limited to the bad data reporting as regards connected devices and the odd, one-off (hopefully) issue logging into the web interface yesterday. I've not had any more trouble with that.
Surely I can do something to make this thing go crazy! When I get a few minutes to spare, I'm gonna start playing with static IP assignments and unplugging the ethernet cables to the satellites so I can try out the wireless backhaul.
But what I probably really need to do is learn how to telnet into the router and disable the auto-update process before a new update is force fed to us (since I haven't had that experience yet). I assume that needs to be done to the router and both satellites?
Has anyone explored the power settings for each band? Or are you guys leaving it at 100% all the time? If you changed it, why did you do so?
Lol. Well the honeymoon appears to be over. I cannot log into the web interface this morning. Keeps asking for the UID and password and says the connection to the site is not private. It's still routing and functioning normally, but I cannot do anything on the router page. I can log into the debug.htm page for the router, but not the main interface.
Interesting. After so many attempts, I get the attached error page.
orbirick wrote:
I can log into the debug.htm page for the router, but not the main interface.That is strange. However, I have noticed that whenever I log in to the debug.htm page first and then delete just "debug.htm" in my browser's address bar, I get returned to the main interface without having to log in again.
tagteam wrote:
orbirick wrote:
I can log into the debug.htm page for the router, but not the main interface.That is strange. However, I have noticed that whenever I log in to the debug.htm page first and then delete just "debug.htm" in my browser's address bar, I get returned to the main interface without having to log in again.
And now it’s letting me log into the web interface. Go figure.
I think it’s toying with me. Tempting me to return it. It better not push very hard. With all the problem reports, I feel like I’m just waiting for the ax to fall.
About 11 hours ago, I reloaded 2.1.1.16. This time I used 'address reservation" for family sanity devices (tv, iPad, iPhone) and various iot devices and the satellites. The addresses used was below the unassigned DHCP range. since then, I haven't observed the satellites dropping off or doing the x.x.x.150 thing. Watched two Netflix movies and some YouTube videos with no issues. No disconnects with iPhone/iPad gaming. No kid telling me how the wifi is glitchy.
I didnt reserve addresses for the laptops and desktops. Those lost connection with a few saying IP address conflicts.
Its a roundabout way to say I suspect the dhcp server. I'll probably sing a different tune when the kid gets out of school in the afternoon.
Shotround -- I also suspect the DHCP server. I was able to observe my AppleTV successfully connect to WiFi but then fail to obtain an IP address. The Apple device defaulted to the fake private IP they use after a timeout. So clearly, something prevented the DHCP server from issuing an address to the AppleTV.
I may try to reserve some addresses as well (although I am not touching anything for the moment as things seem to have calmed down). In response to the Orbi WiFi freaking out I immediately "wired" everything that was close to a hub. Now most of my high bandwidth stuff like media devices is off WiFI -- and that seems to be helping.
yesterday morning, 18 hours after I did the address reservation, communication between one of the satellites and router was out. I had a tv wired to the satellite. The kid's iPad was probably connected same satellite. I reset both as family wanted their morning internet fix.
Its about 27 hours since. Family hasn't complained. I did notice some lag time spikes up to 500ms with iPhone gaming (world of tanks), but no disconnect.
The other satellite is going strong. I haven't touched it since the other day, after flash to 2.1.1.16. It has nas and my computer wired to it.
I have 5ghz at 50% and 2.4ghz at 25%.
I take it back. I'm going back to 2.0.0.74
Hi, I am from HK and brought the RBK53 0n 310/12/2017. It was on 2.0.0.74 out of the box and no auto-update was effected by the system.
Except for taking sometimes to set up wired backhaul, which was not supported in 2.0.0.74 but the salesman told me it was possible, the system has been working prefectly. I have been up for 2 days and 9 hours now. No reboot, no wifi dropping and with around 15 devices attached. I have DHCP enabled and 2 deviced with fixed ip (network printer and NAS for access by applications)
I have also downloaded the 2.1.1.16 but choose not to upgrade for the time being. Will see the development.
Update from testing here. Two satellites both WIRED through switch to router. Entire mesh is 2.1.1.16, but I manually downloaded the 2.1.1.16 satellite file from Netgear and re-installed over the existing file. (Figured earlier update might have gotten corrupted).
TESTING FROM EARLIER - saw a couple devices identifying to which satellite or router they were connected, but now 30 mins later, all 45 devices only show "Orbi Router" as their connection point under "attached devices".
For the devices connected DIRECTLY TO THE ROUTER, they show 2.4 or 5 and a wireless icon under "connection type". This is good.
All other devices, however, are showing Orbi Router as connection POINT but "wired" as connection TYPE. I have no idea to which satellite they're connected, thus can't determine the optimal placing of satellites for fixed devices (e.g. Chromecast connected to TV).
NEST CAMS: so far, so good. Under 2.1.1.16, no frequent disconnect like I used to go.
ROUTER: does not reboot but it's only been working about 12 hours.
The devices not showing to which satellite they are connected is a known issue and the forum moderators have stated that Netgear is working on a fix for next firmware release. 2.1.1.16 is relatively stable, but I did run into an issue after running about a week on it where some devices could not connect to internet through Wifi, even though they are connect to Wifi just fine and able to access LAN. The only thing that seemed to fix this was rebooting the router. I hope that this was just a one time occurance, or is because of some memory leak that will be fixed with next firmware and does not occur more than once a week.
Haha, since the FW update, my satellite thinks it's my Android Phone that I used to initially set things up (see attachment).
So, um, yeah, it's a satellite, not a phone
Mind you, I've done factory reset of both the router and the satellite since then and only set up with the web interface, yet some routing table or similar still has data embedded that tells the router/satellite that the RBS50 satellite is my LG V20 Phone in terms of name and graphic, but it identifies the product type correctly. I manually changed the name back to RBS50 before taking the screenshot.
What a half-baked POS effort from an otherwise great networking gear company...so disappointed in Netgear.
Yes, I'm having 4-6 internet drops a day from my RBR50 router under all FW patches.
While looking at my connections to answer a question above, I decided to pull the cable running from the RBR50 to my PC, and run the cable from the office Gb switch to the PC. Somehow in the process, I managed to dislodge the patch cable running from the RBR50 to the Gb switch which obviously killed my interenet.
No big deal, I simply replugged the patch cable back into the switch, and for good measure, decided that 7 days up time was good enough and rebooted the router.
Before I rebooted the router, I noticed a slight change in the Show statistics page. Earlier looks at this page showed LAN 1 and LAN3 up, but LAN2 down. After the cable mishap, I noticed LAN1 and LA2 were down. The reboot didn't change anything.
What exactly does LAN1, LAN2, and LAN3 indicate? Is that the wireless backhaul LAN?
For good measure, I hit resync on the router, then hit the resync buttons on both satellites within 2 minutes. The top lights appeared to cycle normally and are now back off.
What does this tell me?
7+ days of uptime since I installed the RBK53 system and online updated from 1.12.0.18 to 2.0.0.74, then manually updated to 2.1.1.16.
I do not use the Disney Circle option, and telnet is disabled so far. All satellites are wired.
I sure wish I had some idea what distinguishes my system from those with issues. NG would do themselves a huge favor by figuring this out sooner rather than later.
It sure keeps my interest hearing of systems that ran for months, then mysteriously began having issues after an auto update to 2.x. Makes me glad I bought at Costco in the event I find I need to return it.
Sorta kinda remaining in trust but verify mode with this wifi system.
Was having no problems with the Router + Sat combo. Seems the Nest cams are more stable under 2.1.1.16.
Did the unthinkable and router a 2nd sat today. Had issues adding it... Once settled, would not identify correctly where things were connected. .... Redownloaded 2.1.1.16 to redo the satellites just in case things were corrupted initially.
Magically, Administration/Attached Devices now works, although might still be a bit fishy. Devices don't seem to stay with the satellite with they're connected to - generally shows more the main Router as connection.
Will monitor stability. Nest Cams seems very stable. Earlier versions of Orbi firmware determined by Nest as incompatible with their cams. Maybe this one is better.
Orbirick, are you using your Orbi as a router and access point or just an access point? Do you have any advanced features enabled? Do you have devices plugged into the Ethernet ports on the Orbi or your satellite?
I use mine as an access point only and have multiple devices plugged into the Ethernet ports on the Orbi. Everything else is stock (no advanced features are enabled). I didn't manually upgrade to 2.1.1.16. As soon as my Orbi auto-updated to the new firmware, I had the random reboots.
robertcdh wrote:Orbirick, are you using your Orbi as a router and access point or just an access point? Do you have any advanced features enabled? Do you have devices plugged into the Ethernet ports on the Orbi or your satellite?
I use mine as an access point only and have multiple devices plugged into the Ethernet ports on the Orbi. Everything else is stock (no advanced features are enabled). I didn't manually upgrade to 2.1.1.16. As soon as my Orbi auto-updated to the new firmware, I had the random reboots.
I replaced my old router (RT-AC56U) and AP (RT-N66U) with the Orbi system. I have cat 5e and cat 6 cables run to the satellites. The router is on one side of the house where the internet (fiber to the house) enters to the modem. I have a cable from the modem to the wan port of the RBR50. Then I have a cable from the RBR50 to an 8 port Gb switch (office switch).
From the office switch, I have cables running to my PC and printer, and then 2 cables mentioned above. One goes to a satellite near the center of the house from which I have a cable going to a 4k TV and another cable going to a Chromecast Ultra.
The other cable from the office switch goes to another Gb switch on the other side of the house from which I have cables running to a 1080p TV, Amazon Fire TV, PS3 and PS4 gaming systems, and the other satellite.
I've done very little customization thus far: just opened up the DCHP pool to: 150-254 so I have plenty of IP addresses available.
Under Setup:
-Internet Setup is stock.
-Wireless setup: changed the SSID name to Orbi (how original!), 2.4 GHz channel manually set to channel 1 (did my own site survey using Wifi Analyzer), 5 GHz channel auto set to 48, WPA2-PSK (AES) is checked, and my security password is entered.
-Guest network has not been enabled, all settings stock.
-WAN setup is stock
-LAN setup modified as above.
-QoS setup left alone.
-Telnet is not (yet) enabled.
Under Security:
-No parental controls are utilized.
-Everything is stock.
Under Advanced Setup:
Wireless settings: the only changes are to enable Implicit Beamforming, MU-MIMO, and Fast Roaming. WMM is also enabled if it was off in the stock settings. I should probably disable daisy chain topology as with my wired satellite setup, I don't think DC is useful. Although it probably doesn't hurt anything either by leaving it alone.
-Router is in router mode.
-No static routes assigned yet, but that is something I eventually plan to get around to doing (outside the DHCP pool) for:
main PC, printer, both satellites, and probably a number of mobile clients. No reason to do so, except that I can. ;)
-UPnP is disabled.
Everything else is stock.
