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!
896 Replies
This new firmware is with serios bug. My STB couldn't boot now if i reboot it. After some period of time STB showing that "Server error. Authorisation couldn't be done". It's due to that STB couldn't get connection to ISP server (URL) that loads IPTV services and STB UI for working of IPTV and thus authorisation checks fail also too. And if IPTV services allready are booted normally VOD service is not working, if i try to play VOD video there is no stream and immideatly TV stream stops and there is no picture till i switch to another channel. With previous firmware version 1.0.9.14 it's ok. My ISP provider is Rostelecom.
James,
This router was rock solid for me until the v1.09 firmware update. I now regularly lose all 2.4Ghz connected devices, but 5Ghz devices are fine. It requires a router reboot to restore. Time to failure of the devices appears random, I don't think it is occuring at DHCP lease renewal. I wish I could just migrate all my devices over to 5GHz and be done with it, but I have security cameras and a few other devices that only support on the 2.4 GHz band. Given my occassional travel, I have been forced to enable remote access just to reboot the router, which I hate doing as it opens another vector for attack by an adversary.
After clearing the logs and waiting (is NTP not setting the router date/time correctly), I see the following (MAC addresses are scrubbed):
[Admin login] from source 192.168.1.13, Friday, Dec 08,2017 11:35:22
[DoS attack: Smurf] attack packets in last 20 sec from ip [192.168.1.130], Friday, Dec 08,2017 11:30:13
[DHCP IP: (192.168.1.28)] to MAC address zz:zz:zz:zz:zz:zz, Friday, Dec 08,2017 11:29:38
[DoS attack: Smurf] attack packets in last 20 sec from ip [192.168.1.130], Friday, Dec 08,2017 11:25:43Obvisouly, this is a false positive; otherwise, I would most likely not be to post this.
If I had more time right now, I would just try to an open-source firmware, but I don't. I'm going to try the AC3200 when it arrives and see what happens. I don't see community postings complaining about lost connections with firmware updates on the AC3200. I'm not happy about purchasing a new router just to work around a dev team's bug.
Michael Robbeloth
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.
I'd like to add another "me too" to the group with a bit more information about my setup, as it has been working for the last 24 hours without issue. Since the last update, I would be lucky to go 4 hours without having a Wireless issue.
Having updated the firmware a couple of days ago, I remember reading a post about turning QoS on and off (with a reboot between changes) to clear the database. I had to do this earlier in the year as well when the Router kept dropping wired connections. After that, I did a complete reset of the Router by holding down the reset button in the back for 10 seconds. I then entered all the wireless information again (separate 2.4 and 5GHz SSIDs and Guest networked turned on for each band as well). I did this twice, as the first time, I did it, I was running an older version of the f/w. I also went out and bought an ASUS RT-AC86U as a backup in case things don't improve.
The wireless is working today, and fingers crossed it will continue to work. If not, then it's goodbye to Netgear, and I'll take my chances with Asus. I'll update this post if the problem comes back.
Looks like I spoke too soon. My 5GHz network dropped after about 28 hours. I temporarily switched some of my devices over to 2.4Ghz , which is working at the moment.
It looks like it's time to switch to a new Asus router. I may come back later to see if this is resolved, but I just can't afford the downtime in my personal and professional life. This is my 2nd Netgear Router that I've had to abandon after the WNDR3700 had wireless issues a few years ago as well. As much as I believed in the old Bay Networks/Nortel company, I just can't support being a Beta tester for a production router for a company that has this clear lack of understanding of customer care and support.
Wrocky wrote:I'd like to add another "me too" to the group with a bit more information about my setup, as it has been working for the last 24 hours without issue. Since the last update, I would be lucky to go 4 hours without having a Wireless issue.
Having updated the firmware a couple of days ago, I remember reading a post about turning QoS on and off (with a reboot between changes) to clear the database. I had to do this earlier in the year as well when the Router kept dropping wired connections. After that, I did a complete reset of the Router by holding down the reset button in the back for 10 seconds. I then entered all the wireless information again (separate 2.4 and 5GHz SSIDs and Guest networked turned on for each band as well). I did this twice, as the first time, I did it, I was running an older version of the f/w. I also went out and bought an ASUS RT-AC86U as a backup in case things don't improve.
The wireless is working today, and fingers crossed it will continue to work. If not, then it's goodbye to Netgear, and I'll take my chances with Asus. I'll update this post if the problem comes back.
Looks like this update fixed my problem. There is a known 'feature' of Android struggling to switch between wifi radios. My Nighthawk seemed to also struggle with this. I've been monitoring all morning. Steady as a rock. No drops, No T4 or T5 errors.
I've been tweaking my router for months to solve this issue. FYI: I'm not a Pro, but fairly knowledgeable. I know IP, but not hardware.
What did you do? I read the release notes, but they were a marketing consumable.
Also, my signal strength went up 14% and I haven't touched a thing.
brdoddsjr wrote:Looks like this update fixed my problem. There is a known 'feature' of Android struggling to switch between wifi radios. My Nighthawk seemed to also struggle with this. I've been monitoring all morning. Steady as a rock. No drops, No T4 or T5 errors.
I've been tweaking my router for months to solve this issue. FYI: I'm not a Pro, but fairly knowledgeable. I know IP, but not hardware.
What did you do? I read the release notes, but they were a marketing consumable.
Also, my signal strength went up 14% and I haven't touched a thing.
What problem was fixed for you? Most here are posting about loss of device connectivity on the 2.4GHz radio, an issue which often doesn't show up for over 24 hours. Many, including I, have confirmed that this update did not fix the issue.
That is exactly what got fixed for me. Android has a known flaw that I believe is the root cause of my problem. The Nighthawk did help. Now it lets devices switch radios with delay. I've been working on this for months. BTW most of my devices are static or reserved IPs
I just did an update tonight. It said to wait about 2 minuntes. Nothing ever happened. The screen is frozen and the light on the router flashes white and looks like red sometimes. Any ideas?
- You may have to tftp a firmware to your device. Please Google that and don't pollute this thread.
I was on V1.0.7.6_1.1.99
I upgraded to V1.0.9.18_1.2.27
First halfway thought the upgrade the loading bar turned into a webpage loading error.
red ish lights flashed on the router and i could no longer open up any websites.
I waited for 5-10mins and it continued to flash.
However the blizzard messing service still worked.
I eventually reset the router afterwards speed tests results were 75ms latency .40Mbps download 1.66Mbps Upload.
When i removed the router i was able to get my normal speeds. After reading the forums i see it was a bad idea to upgrade.
I reverted back to my previous firmware and speeds returned to normal.
JamesGL wrote:Please post here for any update/issue related to the latest firmware 1.0.9.18.
Hi JamesGL,
I wonder if you guys are doing anything with the feedback you're receiving. While your customers are left in the dark, with failing networks (personal and professional), I get the feeling you don't take this issue very seriously. At the moment your users are frustrated and disappointed, for the way Netgear is handeling this. That can't be the mission of Netgear, I guess.
Bugs can comeup anytime, that's something we all have to accept, but the way a manufacturer reacts on it, is what defines its reputation.
And let me say... the way Netgear reacts on this issue, that affects alot of users, is very (very, very, very!) frustrating.
Please make this issue a priority and release a bugfix, because this is not the way to go!
Best regards,
Jazzpr- Are other people seeing the "DoS attack: Smurf" in the router log when the 2.4Ghz band devices drop off like mrobbeloth reported? Just wondering if there is anything in the log that points to the problem for more than one person here...
No difference with F/W 18 for me. Worked for about 20hrs and then all connections dropped off - attached devices page on router showed no 2.4 or 5G connections. Going into Wireless setup page and pressing apply to restart wifi cures the issue. Tried multiple channels and all seem to have the same problem
Looks like going to have to buy a new router.
- Update to my previous posts about 18...its been about 35 hours since i downloaded and installed 18. So far everything is still connected. I havent gone this long without disconnecting for quite some time. I am waiting for disaster to strike. The problem is i havent done anything different than most of you guys. One thing i didnt do was factory reset. If the connection stays solid, i will try to help out here, if i could.
