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!
Woke up this morning to find my router shut itself down (or died) at 04:39 (GMT). Tried power cycling it and nothing lights up at all. Didn't have time to investigate further.
I tried open source firmware and the problem had gone away completely. It had been about 5 days, and no connection drops yet.
Seperately Google devices on your network could be causing the connection dropout issues:. Please read the following post:
https://gizmodo.com/your-chromecast-or-google-home-might-be-screwing-up-you-1822112926/amp
Seperately Google devices on your network could be causing the connection dropout issues:. Please read the following post:
https://gizmodo.com/your-chromecast-or-google-home-might-be-screwing-up-you-1822112926/amp
I have 2 Google Home mini's on the XRWT Vortex (latest) firmware and have had no problems with them. Not sure if this firmware is more robust or if it an interaction with NG firmware that is causing some problems.
Don't see how the G Home dump is any different from p2p packet bursts, which are a routine test for throughput and shouldn't hobble a router. Some routers handle lots of small packets poorly, the stock R7000 is one of them. Others do well, Asus for example. Xwrt-vortex is, as you probably know built around Asus firmware and vice versa, and their excellent GUI. Our xwrt-vortex just sails along, no issues at all. It discovers more than twice as many networks as netgear software, over 50 neighboring networks and never stumbles.
Firmware does have a huge effect, the R7000 hardware seems fine.
Not looking back at this point, Xwrt-vortex works so well.
ENuff wrote:Don't see how the G Home dump is any different from p2p packet bursts, which are a routine test for throughput and shouldn't hobble a router. Some routers handle lots of small packets poorly, the stock R7000 is one of them. Others do well, Asus for example. Xwrt-vortex is, as you probably know built around Asus firmware and vice versa, and their excellent GUI. Our xwrt-vortex just sails along, no issues at all. It discovers more than twice as many networks as netgear software, over 50 neighboring networks and never stumbles.
Firmware does have a huge effect, the R7000 hardware seems fine.
Not looking back at this point, Xwrt-vortex works so well.
Yes, you're absolutely right, the hardware is fine but the NG firmware is a disaster right now. I really don't understand why some of the forum users buy new hardware without trying alternative firmware first. In their perception the router is broke already. Why not flash XWRT-Vortex (one of the best R7000 firmware there is) before throwing away the router.
wifiuser123 wrote:
I tried open source firmware and the problem had gone away completely. It had been about 5 days, and no connection drops yet.
Seperately Google devices on your network could be causing the connection dropout issues:. Please read the following post:
https://gizmodo.com/your-chromecast-or-google-home-might-be-screwing-up-you-1822112926/ampThere might be some truth to this issue with Google devices such as Chromecast and it messing with wifi. I have 4 Chromecast devices on my network.
http://bgr.com/2018/01/15/google-chromecast-home-wifi-problems-router-crashing/
Google has confirmed an issue with its Google Home and Chromecast products that can cause your home Wi-Fi network to crash. According to a TP-Link engineer who investigated the problem, the crash is caused by Google’s device sending hundreds of thousands of data packets in a short amount of time, a traffic spike that can crash routers commonly found in your home.
The issue reportedly affects routers from ASUS, Linksys, Netgear, TP-Link, and Synology, which covers most brands you’re likely to find in your home. A Google spokesperson seemingly confirmed the issue to 9to5Google, saying that Google’s engineering team “is working quickly to share a solution.”
In a post on its FAQ page, TP-Link explained what it had discovered to be the problem:
Following initial research and investigation, our Engineering Team is confident that they’ve determined one of the key origins of the issue. From what we have gathered so far, the issue appears to be related to some recent releases of Android OS and Google Apps. This issue stems from these devices’ “Cast” feature, which sends MDNS multicast discovery packets in order to keep a live connection with Google products such as Google Home. These packets normally sent in a 20-second interval. However, we have discovered that the devices will sometimes broadcast a large amount of these packets at a very high speed in a short amount of time. This occurs when the device is awakened from the “sleep mode”, and could exceed more than 100,000 packets in a short amount of time. The longer your device is in “sleep”, the larger this packet burst will be. This issue may eventually cause some of router’s primary features to shut down – including wireless connectivity.
TP-Link has fixed the problem for its users with a firmware to the router, which should allow it to handle the sudden burst of packets without crashing. If you’re experiencing similar problems with a different router, the only solution for now appears to be to unplug whatever Google device is causing the issue. Hopefully, a software update is on the way.
The Google thing may well be the cause for some drops for some people but it wasn't the case for me, I don't have any.
