Yep, it is all a question of money they do not wanna spend on it,
and we mean moral banktruptcy of firmware here,
that is why there is so many hacks an IoT malbots around.
Situation is not gonna change soon and we have to fend for ourselves, dear Eddy.
Change software to XWRT-Vortex seems to mitigate the problem (info credits: @tigs)
suswrt-Merlin (or XWRT or Cross-WRT) firmware for Netgear R7000 router.
At this point when you have a working version based on a Asuswrt-Merlin v380.63_2
that does not requires to flash the custom CFE. Firmware is pretty stable.
Download links:
XWRT for Netgear R7000 v380.63_2 is here
(previous versions are also available at this link)
Official site, Changelog. ->
http://www.kb.cert.org/vuls/id/582384The recommended procedure for initial flashing:
1. Reset your router to factory defaults via the web interface.
2. Flash the R7000_xxx.xx_x.chk file via the web interface.
3. Do another factory reset via the new web interface.
4. Configure everything else.
Procedure for upgrade:
1. Reboot your router via the web interface or power cycle.
2. Flash the R7000_xxx.xx_x.trx file via the web interface.
3. Check new options and configure everything else.
Link to the "back to stock" firmware (v1.0.3.80_1.1.38) is here.
Important: If You want to go away from XWRT back to tomato or dd-wrt
you MUST first flash the "back to stock" firmware image, or you will brick your router.
polonus