NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

JamesGL's avatar
JamesGL
NETGEAR Employee Retired
Dec 18, 2017
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. 
Firmware
  • FURRYe38's avatar
    FURRYe38
    Mar 07, 2018

    You should review this and maybe revert back to this recommended version of FW:

    https://community.netgear.com/t5/Nighthawk-WiFi-Routers/R7000-1-0-9-26-Feedback-Thread/m-p/1520141#M85677

     

    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!

     

hellspawn69's avatar
hellspawn69
Guide
Jan 18, 2018
My fix works. Someone who hasn't loaded custom firmware is welcome to check it out. Takes no time to make the changes I did, and mine has 0 issues dropping the 2.4GHz bands now.
Just trying to help fellow frustrated customers out since Netgear doesn't seem to be.
jimbau's avatar
jimbau
Aspirant
Jan 18, 2018

So, what is your fix?

  • potamus29's avatar
    potamus29
    Guide
    Jan 18, 2018
    It's gone quiet because either, people have given up with Netgear or, like me, have rolled back to an earlier Firmwear which works and are waiting for the mythical communication from NG.
    • Diggie3's avatar
      Diggie3
      Luminary
      Jan 18, 2018
      Bro, your fix was (aside from all the other settings I've already tried) disabling SSID on the 2.4 band and manually picking a channel. And a request for money via GoFundMe.

      Yeah... no.
      • hellspawn69's avatar
        hellspawn69
        Guide
        Jan 18, 2018
        The gofundme was just to be funny. Like the Internet is randomly gone give me a car lol.
        Disable your broadcast of SSID and the 20/40 coexistence and manually set a channel. I'd honestly love to know if that doesn't solve the problem for you. I have 0 issues since I did that. What can it hurt you to try except maybe manually configuring a few endpoints to still hop on the hidden network.
    • mhsu858's avatar
      mhsu858
      Guide
      Jan 18, 2018

      This lucky combination fixed my problem (staying with 1.0.9.18).  stable for 10 days now.  before, I had to reboot router 2-3 times a day for dropped devices to reconnect (getting stuck at getting IP).  I have 23 devices, 5 of them google phone/home.

       

      router config:

      use smart connect - single SSID for 2.4 and 5G
      use Google DNS
      Use reserved IP for all devices
      no guest network
      no QoS
      no UPnP

      no readyShare
      WAN setup - defaults
      LAN setup - defaults + add address reservations
      WPS - disabled
      Wireless setting -
      2.4G - channel - 1 (found weakest neighbor -95 dBm on channel 1)
      WPA2-PSK
      enable 20/40 coexist
      5G - channel 40 (not able to see neighbor's)

      • mhsu858's avatar
        mhsu858
        Guide
        Jan 18, 2018

        And, should not forget this seems to be the most important one for me:

        Enable "Access Control" but allow any device to connect

  • hellspawn69's avatar
    hellspawn69
    Guide
    Jan 18, 2018
    See post 653