This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I've got Arlo camera's so I'm stuck with the beta firmware. Running: V1.0.6.40_1.1.90 now in AP mode. So far not happy with the R7000 - Every now and then when i login to the router it states: "Updating Settings" and it will reset the modem. Not really great.. as you can imagine. I can, after the reset, login to the router. - Some Arlo camera's are getting disconnect every now and then (1 every 2 to 4 days). Reset r7000 through Arlo app fixes the problem. Never had this issue with the Arlo basestation in place. As you don't receive any push messages when arlo lost it's connection this is not great.
Is there any new firmware implementing a more stable connection.. otherwise i will need to hook up the basestation again... 😞
Hi everyone, i wish to provide my feedback on R7000. So i own this device since 2 years now and i've tried every firmware out there because i basically wanted a nas in my router and stock firmware didn't provide enough features for me. Now i'm back to stock since transmission(aka netgear downloader) was added to it. My experience with all firmwares and 1.06.28 has always been rock solid, i didn't experience any of the issues people on this thread posted so i think that the problems people are facing might be related to hardware somehow. People who buy R7000 today might have slightly different hardware than those who bought it on release or whatever.
Most of the user's problems on this forum is the reluctance to reset their router's to factory default after upgrading firmware (this version or others).
Most of the user's problems on this forum is the reluctance to reset their router's to factory default after upgrading firmware (this version or others).
Please STOP perpetuating this myth! I take a lot of umbrage with this comment, because there are tens or hundreds or thousands of us who do not have the bandwidth to sit here on this message board and debunk you and a few others, and we spent a LOT of time resetting and re-configuring our R7000s while you sit there and contribute to the misinformation.
What is clear from this debacle is that Netgear has two issues
1) Netgear had severely under-resourced the continued support and development of their products to get to the scenario where we are now
2) There are critical faults in communication amongst Netgear development, QA, and support staff teams
Dear moderators, I know you are trying your best and it's at least clear some changes were made in your approach (for the better!) following the pulling of the broken firmwares. The suggestion I might make is for every post where you recommend a firmware, old, new, or beta, please link to the firmware you are recommending. There are too many posts here where something was said as posted previously, and then we have to go dig or search through hundreds of messages to find what was being referenced, particularly with multiple competing versions. Then we are left scratching our heads when there are links posted from random people to Dropbox files, which is weird enough as it is when it's officially coming from Netgear staff.
One hypothesis: my (breaking) R7000 is used in a highly saturated, dense, urban environment with lots of wifi and bluetooth and wireless signals clashing throughout. Perhaps the reason some of us are impacted whlie others are not has to do with this environment vs those in the boonies with clear airwaves. Just a thought because I've seen it before.
Most of the user's problems on this forum is the reluctance to reset their router's to factory default after upgrading firmware (this version or others).
Please STOP perpetuating this myth! I take a lot of umbrage with this comment, because there are tens or hundreds or thousands of us who do not have the bandwidth to sit here on this message board and debunk you and a few others, and we spent a LOT of time resetting and re-configuring our R7000s while you sit there and contribute to the misinformation.
What is clear from this debacle is that Netgear has two issues
1) Netgear had severely under-resourced the continued support and development of their products to get to the scenario where we are now
2) There are critical faults in communication amongst Netgear development, QA, and support staff teams
Dear moderators, I know you are trying your best and it's at least clear some changes were made in your approach (for the better!) following the pulling of the broken firmwares. The suggestion I might make is for every post where you recommend a firmware, old, new, or beta, please link to the firmware you are recommending. There are too many posts here where something was said as posted previously, and then we have to go dig or search through hundreds of messages to find what was being referenced, particularly with multiple competing versions. Then we are left scratching our heads when there are links posted from random people to Dropbox files, which is weird enough as it is when it's officially coming from Netgear staff.
One hypothesis: my (breaking) R7000 is used in a highly saturated, dense, urban environment with lots of wifi and bluetooth and wireless signals clashing throughout. Perhaps the reason some of us are impacted whlie others are not has to do with this environment vs those in the boonies with clear airwaves. Just a thought because I've seen it before.
Thank you
Yeah, as any vendor, NG has their fair share of firmware problems.. It's no myth. The logic is very simple, actually. Not only NG, but other vendor's suggest the same thing. Reason being is this.. The only way to correctly load any new drivers, or any new features is is to do a factory reset. The reset gets rid of old config and firmware artifacts.. So, myth busted!!
I run various flavours of firmware, stock and 3rd party. Mostly 3rd party firmware actually. I can change back and forth between stock, and 3rd party firmware, all day long, and not have any issues. Never had an issue. And if I do, then I know where to point the finger. Same goes with configs with different firmware versions, for obvious reasons, you would not load an old config, with new firmware.
And for all you people too lazy to follow this advice, and whine because you have to re-configure your router, alI can say is, enjoy your pain. If this stuff is over your head, then buy a product that you actually manage, or pay someone to manage it for you.
Oh, and I don't live in the boonies!!! But, here's a tip. If you live in a heavily populated wireless area, upgrade your stuff and migrate to 5ghz, or better yet, buy Ethernet cables and plug in!
If you live in a heavily populated wireless area, upgrade your stuff and migrate to 5ghz
This does not solve the original problem and may introduce new problems. Additionally, certain devices may only work on one frequency band. Regardless, the R7000 provides both frequencies.
For those of us with networked environments, we have found the issues we are discussing here are only relevant to the wireless side of the R7000 device. The wired side has been stable, at least in my experience.
Actually he is right. No other way to get rid of old configuration and garbage.
But if you're so sure, why don't you explain why it's factually false?
I suggest you pose your question to the developers and ask why they don't make a reset mandatory for all customers at every upgrade. I also suggest you ask that question to any software developer or developer of embedded systems, generally speaking.
They always done it if FW has many fixes or changes, also in brief "what is changed or new" they has a warning that it is reccomended to do a hardware reset after an update. The problem in that not all read that or read not carefully.
Not knowledgeable enough to know about the factory reset, but I do know I was having serious connectivity issues with .28 so I upgraded firmware to .40, without a factory reset, and the system, so far, appears to be rock solid!
Actually he is right. No other way to get rid of old configuration and garbage.
But if you're so sure, why don't you explain why it's factually false?
I suggest you pose your question to the developers and ask why they don't make a reset mandatory for all customers at every upgrade. I also suggest you ask that question to any software developer or developer of embedded systems, generally speaking.
well I'm asking you, because you said "that's factually false" so when using those terms, it means you know exactly what you're talking about. So please, since you do, share. Enlighten us.
Otherwise, please stop being so condecendent and do try a factory reset before and after a new firmware...
do try a factory reset before and after a new firmware...
The issues still continued to occur for people after performing a factory reset. That was the point of all this.
I had the same problem as the others when I upgraded to the latest available firmware, but wanted to do it fast so skipped the factory reset after the upgrade. Ran into some troubles, was pissed off, wanted to throw the router to the wall. But decided to spare my wall, so I did a factory reset *before* and *after* the upgrade, and since then, my router has been running great and my wall feels better.
upgrade, and since then, my router has been running great and my wall feels better.
That is another data point, however people on this message board should not apply their own anecdotal experience to everyone, much like my anecdotal experience of continued failure after factory reset does not apply to you.
upgrade, and since then, my router has been running great and my wall feels better.
That is another data point, however people on this message board should not apply their own anecdotal experience to everyone, much like my anecdotal experience of continued failure after factory reset does not apply to you.
This is a forum, people share their experience so that they can solve their problems with their router...
What do you expect to read on this forum but bad experiences? When people are satisfied, they don't come here.
Or when they do, it's to help others. That's what I'm trying to do. I've had a good experience with this upgrade, so I share.
I don't want to get into a pi**ing contest here, but there is NO speficic 'must do'. I suspect any drivers should come in with the new firmware, however DATA might not get erased/overwritten.
I would think during a flash ALL the s/w would be replaced, BUT the data areas might not be. Since it is clear, especially with Beta versions of the F/W or going back to an older F/W version NOT to use the backup settings file, once an assume that exact data locations used might 'move' and the wrong data picked up if one does ensure ALL data used was correct. Either one needs to look at every possible setting or RESET and redo settings. I would also assume the big difference in data locations would be new feature settings. Old ones, like SSID's, P/W, and older items that remained the same would still point to the same data location more than likely.
However, the safest would always to reset and redo the settings. Of course, one could always 'wing' it and see if there is a NEED to do that?
I do not think the need to reset is a HARD and FAST rule.
They always done it if FW has many fixes or changes, also in brief "what is changed or new" they has a warning that it is reccomended to do a hardware reset after an update. The problem in that not all read that or read not carefully.
