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!
Same problem here, WIFI issues with Samsung phones after V1.0.9.14_1.2.25. (.14 version is the one that works.)
1.0.9.18 and 1.0.9.20 (hot fix) do not fix this issue. So I have to run a router with a number of known vulneratbilities, it is a shame. The Q/A at Netgear is lacking severely, this is all preventable with automated testing of new FW roll outs. IMO they should point out the problems with the Samsung phones and also keep readable bugs for their end users. The time that gets lost by millions of individuals having this figure this out is immense. And also the good ones that try to keep their routers up to date get punished the hardest.
Bought a new router (tplink) before flashing tomato on the r7000: what a relief. R7000 is functioning as an access point while the c5400 has become the ‘mainrouter’. No slow data throughput anymore, no 2.4 ghz WiFi problems.
- I too am likely to go back to 1.0.7.x today.
This is a total joke. Not only am I wasting my vacation troubleshooting my network, but also my home automation and security is also unreliable as a result.
It is amazing that NG still has no fix. This is so bad!- Diggie3 It is useless to go back. I already tried that, no Netgear firmware can fix it. Install Advanced Tomato, it is great and has a lot of features Netgear doesn't have.
Has Advanced Tomato fixed the KRACK vulnerability? I can't find anything verifying a patch.
