NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Feedback for R7000 New firmware 1.0.9.18
Hi All,
Please post here for any update/issue related to the latest firmware 1.0.9.18.
You should review this and maybe revert back to this recommended version of FW:
Alfikwrote:I've looked here again after a while and I can't belive the problem is still not solved....
Since I've flashed Tomato a few weeks ago I've forgotten that I have a router- it's working perfectly getting dust because i do not touch it at all :-)...
Parental control works perfectly, 0 drops, strong signal - save your time and do a similar thing!
NETGEAR: PLEASE READ THIS AND REPLY!!!
You have a massive loss of confidence brewing here, and a potential loss of many customers for years. You might also start to get bad press in public soon. I have some ideas to help you resolve this. Please escalate this appropriately within Netgear, or you may lose millions of dollars in sales due to mishandling of this issue. If you are reading this and work at Netgear, and your feel you must follow an internal process that will cause this issue to remain unsolved for weeks or months, I suggest you step outside that process. You may end up being a company hero.
Do you understand the root cause of the issue yet? If so, please update the forum to instill confidence and prevent people from wasting their time guessing and trying random firmware fixes, ones that potentially expose them to security flaws you worked so hard to fix in the past.
If you do not understand the root cause, consider: some people's issues apparently are resolved by restoring older firmware, and some people's are not. Ensure your lead engineers in charge of this issue ARE AWARE OF THIS. Then, please answer: what aspects of a router's operation might remain by going from firmware A, to firmware B, then back to A again? What is different at the end of this process that might reveal a bug, that was not present when Firmware A was in operation for weeks or months? Is there a secondary memory somewhere in the router beyond the chip that stores the firmware? If so, it is in that memory's interaction with the firmware that you'll find a bug.
If not, is there a date coded into your recent firmware?
If one of the above answers are "yes", your problem will be found there. If the answer is "no", then your problem is environmental. You should be asking for dozens of logs from your users to seeing what is going on, on a global scale, that is causing the issues. I imagine it should also be quite easy to replicate this in your lab or among any of your employees who have Nighthawk routers, since this issue is so widespread. With a little effort, you might not even need your paying customers' help or logs at all to fix the issue.
There are no other alternative explanations for what people are observing. Or, if there are, please let us know so we can provide information that may help confirm or eliminate potential sources of the problem.
Above all, please start communicating, or this may destroy your company's reputation for many years.