api

Ok, it looks like it's back up and going for now. I'll let you know if anything else comes up. Not sure what was different this time around with the TFTP stuff... A couple of things to note - my laptop uses a USB-C to Ethernet adapter (Realtek) whereas the second computer I used is an Intel NUC with an Intel I218-LM chipset. Also, I moved the network cable from Eth1 to Eth4. Lastly, the NUC has Windows 7 on it whereas the laptop has Windows 10.

Just tried the TFTP process on another computer (different OS, different network chipset). Now all I'm getting is a power light - nothing at all on the LAN ports. Update - the power light sat orange for a bit and just went to solid white. Update 2 - I can finally get to the web interface on it! Might be getting somewhere...

Notice though, that I'm not the only person in this situation - a couple of people in this thread have run into situations where they couldn't access the interface. The difference with mine is that the TFTP fix isn't actually fixing it.

No, I am not able to access it through either of those links. I have tried the TFTP process 5 times now on version 56 and twice on version 32. This router is now 1 year and 1 month old which puts it out of Netgear's warranty. To complicate things, I am moving out of the country in 12 days and with the holiday I cannot see how I would be able to get a replacement in time even if Netgear did cover it. This honestly could not have come at a worse time. This router was perfectly fine until whatever you changes you made. Unless you can get me a new router before 12/29, I'm going to be stuck with a $270 paperweight which would most definitely be my last Netgear and/or Duma product. Not trying to be a jerk here, but I'm genuinely stunned at how this could have happened.

Nope, still cannot. I'm not able to access the interface nor can I ping 192.168.1.1.

I still cannot access the interface. ipconfig does not show a gateway address because it is not pulling an address with DHCP (despite having the computer set to do so).

I cannot access the interface at all. I also am not able to ping 192.168.1.1. I did not downgrade/upgrade anything prior to rebooting the router. Basically, I got the "DumaOS not loaded yet" message. I went to this page - 192.168.1.1/adv_index.htm and was able to access that. After I was in there, I read that some people were resolving the issue by rebooting the router, so I clicked the Reboot button in the GUI. I saw it reboot and it never came back after that.

I have my laptop plugged into Eth1. I've tried using the TFTP64 GUI client as well as tftp via command line in Windows 10. Steps I followed are - Power router off for >10 seconds. Hold down reset button - while holding reset button, power on router and wait until power LED flashes at least 10 times (goes from orange to white). Release reset button Start "put" of image file using tftp I then get the following message - "Transfer successful: 35268737 bytes in 29 second(s), 1216163 bytes/s"

After using a combination of these steps and the one provided by Brainbleach, I was able to get the TFTP process started. It didn't indicate any error messages or retransmissions, but the router is still not booting. It appeared as though it rebooted, but it's still not showing any more than the power LED and Eth1 lit (where my laptop is plugged in). Any other suggestions?' UPDATE - I tried both 32 and 56 versions of the firmware. No change

Unfortunately, my router appears to have been bricked by this. I went to login to the router and got the "DumaOS not loaded yet" message. I rebooted the router and it is now stuck with just the ethernet port LEDs on and the power LED. The wireless is not coming up at all. I plugged a computer in to a hardwired port and it is not getting any IP address. I tried doing a factory reset with the button on the back - no change. When I hold down the reset button for a few seconds, the power LED goes off but the ethernet ports stay lit. Any ideas on how to resolve this?