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!
For those of you that have flashed your firmware to XWRT-Vortex, have you noticed any difference (increase or decrease) with the range of both 2.4G and 5G compared to the NG firmware?
Rikardo007 wrote:For those of you that have flashed your firmware to XWRT-Vortex, have you noticed any difference (increase or decrease) with the range of both 2.4G and 5G compared to the NG firmware?
In default setting it is pretty much the same but as it is rock stable without dropouts it feels much better. In XWRT-Vortex you can also adjust the TX-power. Default setting is 50% and can be increased. Be aware that you might shortened your hardware lifespan.
It’s them:
Seriously, I don’t have any Google cast devices and don’t have any problems with my R7000. Not on 2.4 or on 5 GHz with fw 1.0.9.18. Stable for many weeks.
- Sorry, I should have been as clear as Rogier64 in that I have left my XWRT-Vortex firmware relatively default, especially with TX power. I am finding the 50% setting works just great for my needs on both 2.4GHz and 5GHz bands.
If you configured your R7000 relatively by default you probably haven't enabled BWDPI yet. Go to Tools->Other Settings and scroll down to Asus features. Enable BWDPI to Yes and click Apply Settings. Reboot the router now. After booting log in to the router and you have AiProtection, Adaptive QoS and Traffic Analyzer added which are very nice features.
I had to jump ship I'm afraid. I need stability on my Wireless setup - Tomato installed. Let's see how this goes...
Just found an article about Google Chromecast and Google Home cause temporarily Wifi dropouts.
This is from an TP-Link engineer. http://www.tp-link.com/us/faq-2050.html.
I don't think this is the issue, but the complaint I read about effects Asus, Linksys, Netgear, TP-Link or Synology.
Still going strong with Tomato.
Name TomatoUSB Model Netgear R7000 Chipset ARMv7 Processor rev 0 (v7l) CPU Freq 1000 MHz (dual-core) Flash Size 128MB Time Sat, 13 Jan 2018 13:53:11 -0500 Uptime 14 days, 16:43:26 CPU Usage 0.58% CPU Load (1 / 5 / 15 mins) 0.33 / 0.09 / 0.07 Memory Usage 35.68 MB / 249.64 MB (14.29%) NVRAM Usage 35.13 KB / 64.00 KB (54.88%) CPU Temperature 57°C Wireless Temperature eth1: 2.4G - 47°C eth2: 5G - 48°C
AaronB483 wrote:Just found an article about Google Chromecast and Google Home cause temporarily Wifi dropouts.
This is from an TP-Link engineer. http://www.tp-link.com/us/faq-2050.html.
I don't think this is the issue, but the complaint I read about effects Asus, Linksys, Netgear, TP-Link or Synology.
........
I came across the article, or certainly similar at: https://www.androidauthority.com/google-home-max-wifi-830129/
which describes a similar issue with the Google Home Max. I wonder how many of us are running Google Home Devices. I am. running a few.
Wrocky wrote:
AaronB483 wrote:Just found an article about Google Chromecast and Google Home cause temporarily Wifi dropouts.
This is from an TP-Link engineer. http://www.tp-link.com/us/faq-2050.html.
I don't think this is the issue, but the complaint I read about effects Asus, Linksys, Netgear, TP-Link or Synology.
........
I came across the article, or certainly similar at: https://www.androidauthority.com/google-home-max-wifi-830129/
which describes a similar issue with the Google Home Max. I wonder how many of us are running Google Home Devices. I am. running a few.
I don’t have Chromecast or Google Home Max; I have a Netgear r7000 and a tp link router. The Netgear has WiFi connection problems but the tp link has not in my configuration. There must be another problem (on top of the problem you describe).
EDIT: after reading more information my conclusion might be not correct: the tp link router affected is the c1200 (I have another type) and a WiFi disconnect can be invoked by a device that is supporting Google Cast (by generating a kind of WiFi packet storm).
- AaronB483 That is very insightful!
I have Google Home devices AND Android phones on Android 8.1 *AND* recently I was debugging them which involved connecting to them with ADB and dumping the device logs with "adb logcat". I can confirm from what I saw it did look like they were sometimes spewing MDNS messages. If that is exhausting memory on the router it could be the problem. - My R7000 2.4GHz Wi-Fi dropped when I was away from home. No Google Cast up and running. No Oreo up and running. Just regular devices which were there before the firmware update. The R7000 firmware update did something wrong with our R7000 systems. I don't think we must blame other devices. Nothing changed in my environment, only the R7000 firmware.
Same here. I have 3 kids and a nanny in my house. I have multiple Nexus Players (chromecast built in) for a couple years, 2 standalone chromecasts for 3 years, 2 Brother wireless network printers (3-5 years), 3 iPads, 3 Android tablets, 1 iMac, 3 laptops, 2 smart TVs, 5 smartphones, 2 wireless IP cameras, 1 Ooma Telo2 (wired ethernet to router), and 1 Google home (since November 2017). I've had my R7000 for a couple years now, rarely had to reboot. Everything was working fine until this friggen .18 firmware update. Tried to revert to 1.0.7.12 (reset afterwards and manually entered all settings) and was stable for a few days, but now still dropping multiple times a day. I do have 4 separate SSIDs (one for each 2.4G and 5G main and guest), no QOS.
I'm one of those "if it ain't broke, then don't fix it". The only reason why I did the update was because I was about to add a HDD to the router (did not connect it yet) and I noticed there was a firmware update. I hadn't updated the firmware since I first set it up and I remember getting a couple emails from NG in the past year regarding security patches. What a mistake.
HWAM wrote:
My R7000 2.4GHz Wi-Fi dropped when I was away from home. No Google Cast up and running. No Oreo up and running. Just regular devices which were there before the firmware update. The R7000 firmware update did something wrong with our R7000 systems. I don't think we must blame other devices. Nothing changed in my environment, only the R7000 firmware.Same issue here. All these disconnects started after the lastest fimware update. Was running flawless for over a year with 0 issues until this update.
- While they claim that is an issue, i have 2 Nexus players and an Galaxy S8 on Oreo and my setup was running fine for months until i updated to the .18 firmware.
- I did read the article. While there may be issues related to some Google products, i did not experience any problems for months until i updated the firmware on the R7000 to .18. I've had my S8 since May and Nexus Players updated to Oreo approx Sept 2017. My issues began within hours of the NG firmware update.
Whilst there are many references to using Google products and Android etc, I have none of these and can confirm that the issues highlighted in this (and other) threads only became apparent 'immedeatly' following the update to the latest version of the firmware. Not only on the R7000 router that is some years old, but on an R7800 router to which I ugraded the firmware straight out of the box.
Whilst the problem may be exagerated by Google, or other products, for me, it is clearly related to the NetGear firmware change - unless we want to start introducing Apple and Synology products to the mix as well.
- To save new people reading dozens of pages, if you want to stick with stock FW instead of Vortex or Tomato until NG puts out a fixed version nearly everyone has stability going back to 1.0.7.12 (March 2017), and some as far up as 1.0.9.6, but generally not after that. If you want 1.0.9.6 you will also have to turn off automatic updates after installing it.
Diggie3 wrote:
To save new people reading dozens of pages, if you want to stick with stock FW instead of Vortex or Tomato until NG puts out a fixed version nearly everyone has stability going back to 1.0.7.12 (March 2017), and some as far up as 1.0.9.6, but generally not after that. If you want 1.0.9.6 you will also have to turn off automatic updates after installing it.About 8 months ago my R7000 became unstable after a firmware upgrade. I never got it stable again, even returning to an old firmware. But test it yourself. I tried different alternative firmware versions and found XWRT-Vortex the best there is if you also want security patches.
I rolled back to FW version 1.0.9.10_1.2.21 five days ago, still ok, no drops.
