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.
howiedub wrote:When did everyone buy their Orbis? Was it when the range was 2,000sf per node, or 2,500sf per node? I have the RBK53, the ...
Where do you see that info? I have the same router from Costco and it's working great now on 2.1.1.16
I bought mine from Costco as well earlier this year. The 7,500sf number is on their website. You can see the 6,000sf number on the screenshot from Slick Deals. When did you buy yours? And how many devices do you have connected? I have anywhere from 26 to over 30 devices connected.
howiedub wrote:
I bought mine from Costco as well earlier this year. The 7,500sf number is on their website. You can see the 6,000sf number on the screenshot from Slick Deals. When did you buy yours? And how many devices do you have connected? I have anywhere from 26 to over 30 devices connected.I got it a little more than 3 months ago when I visited Oregon. Came with 1.x firmware and I did a manual update as it refused to update automatically. Been doing manual updates ever since come to think of it since it's never found any firmware automatically for me - though I am in Vancouver Canada.
Right now it's listing 25 devices and two satellites connected. It bounces up to more than 40 devices when some other things are connected and some family visits.
I've always run it as the router, not an AP.
Stability has been rock solid except for the initial incident that prompted me to turn off UPNP. 1 day and 3 hours uptime now on 2.1.1.16 and all is good.
aaz wrote:
howiedub wrote:
I bought mine from Costco as well earlier this year. The 7,500sf number is on their website. You can see the 6,000sf number on the screenshot from Slick Deals. When did you buy yours? And how many devices do you have connected? I have anywhere from 26 to over 30 devices connected.I got it a little more than 3 months ago when I visited Oregon. Came with 1.x firmware and I did a manual update as it refused to update automatically. Been doing manual updates ever since come to think of it since it's never found any firmware automatically for me - though I am in Vancouver Canada.
Right now it's listing 25 devices and two satellites connected. It bounces up to more than 40 devices when some other things are connected and some family visits.
I've always run it as the router, not an AP.
Stability has been rock solid except for the initial incident that prompted me to turn off UPNP. 1 day and 3 hours uptime now on 2.1.1.16 and all is good.
What version of the firmware were you running right before you updated to v2.1.1.16? I'm asking because I have a theory that v2.1.1.12 caused all the problems and going from v2.1.1.12 to v2.1.1.16 without doing a factory reset does NOT eliminate the problems introduced by v2.1.1.12?
After all i did last night (NVRAM reset, factory reset, and not changing much of initial re-configuration), i woke up this morning to see that both my router and satellite had rebooted (at the same time; their system uptimes were just a few seconds different). Its strange that both rebooted, i thought maybe a power surge, but the router is on a UPS (satellite is not).
Based on another user's stable configuration post, i modified my config to disable daisy-chaining (i only have 1 satellite), as well as disable WMM for both 5 and 2.4 ghz. Since i have an Asus router doing routing responsiblities (and QOS), i am guessing i don't need the overhead of Netgears QOS.
Will keep monitoring