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.
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.
I completely understand. In fact, I read this board, as well as myriad reviews, many times before I bought my Orbi system and I bought it from Costco (as did you, IIRC) specifically because of Costco's unlimited return policy.
Having written that, I have had virtually no issues (other than the current display issue) with my system; firmware version 2.1.1.16 shows 13 days of uptime for me and I had 48 days of uptime on version 2.0.0.74 prior thereto.
Further, I have found that my Orbi, in my personal application, has better range and reliability than any router I have previously owned. I sincerely hope it continues in that regard and ALSO that the more severe issues some are experiencing get resolved soon.
orbirick wrote:
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.
I finally found a solution to my Orbi problems. First, I turned off the satellite. Next, I turned off the router. Then I put both of them in the box they came in and shipped them back to Amazon. That was six days ago. Since then I have been running an Asus RT-AC3100. I just connected it up, did some configuration, and it has been running every since. No self-reboots every few hours. No dissappearing connected devices. It just runs and does its job. It turns out I didn't need a mesh system for my 2800 sq.ft. house. All I needed was a new wireless router with modern features like MU-MIMO and Beamforming. My old router was an AC class router, but it did not have the range of this Asus. Best of luck to those still having Orbi issues. That is one problem I no longer have.
the problem apears to be coming from Android Oreo devices... I verified by turning off wifi on my phone(Oreo 8.1) last night, haven't had any issues with Orbi... Netgear still has to come up with a fix for their end, because no way should a client be able to disrupt and REBOOT a router!
tagteam wrote:I completely understand. In fact, I read this board, as well as myriad reviews, many times before I bought my Orbi system and I bought it from Costco (as did you, IIRC) specifically because of Costco's unlimited return policy.
Having written that, I have had virtually no issues (other than the current display issue) with my system; firmware version 2.1.1.16 shows 13 days of uptime for me and I had 48 days of uptime on version 2.0.0.74 prior thereto.
Further, I have found that my Orbi, in my personal application, has better range and reliability than any router I have previously owned. I sincerely hope it continues in that regard and ALSO that the more severe issues some are experiencing get resolved soon.
orbirick wrote:
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.
I never had any service interruptions today, just that weird period of time where I could not get into the web interface of the router. That issue has not come back, so I guess that was simply an anomaly. I hope.