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!
mzguy wrote:
HWAM wrote:
rudiklein I know all brands can create bugs. But I am not able to repair the R7000. Even a full reset and flash the oldest firmware wasn't fixing the issue. I guess the problem firmwares broke my router.Did you try 1.0.7.10_1.2.3? It appears to be working for some time for two other users.
I tried anything. Also 1.0.7.10_1.2.3. I think my router is ruined by a recent firmware. I don't know if this is possible but I really don't understand it anymore. I work in the ICT and I can't explain this. I'm done with Netgear. I ordered a Linksys WRT1900ACS.
I received a replacement router last Saturday after having all these same issues with dropping like everyone else. I intentionally DID NOT update the firmware when I received it to see if there were any drops in 24 hrs...there were none.
I then upgraded the router directly to the .18 firmware to test it out and in 3 days time I have had zero drops, resets, nothing. Router is running very well. I have Port forwarding on and I'm running both 2.4 GHZ & 5 GHZ together and both have the same password.
When I shipped my old router back to Netgear I used the same box that it came in when I purchased it 7 months ago. I compared the production numbers and noticed the last 3 numbers are different so I wondered if this router was produced later and possibly the earlier produced router came from a defective batch? Maybe not...I'm just brainstorming.
I also wondered if possibly the firmware that caused this initially begin somehow destroyed the router beyond repair. It's just odd I get a router with stock firmware and go directly to this firmware on a new router and I have zero issues but others with this router using the same firmware are still having the same issue. So either the routers hardware is bad from the factory or a previous firmware version has screwed the routers up. I don't see how you could draaw any other conclusion from this mess.