My Netgear Nighthawk x6 R7900 router has been plagued by DNS issues of the OEM firmware for some time. I finally decided to try an open-source firmware, and downloaded OpenWrt from this page
I used the Netgear web GUI and flashed the openwrt.chk file, but then I am no longer able to connect to the router.
The router only has a single power LED on in red. If I connect my laptop to the LAN port, the LED of the port is led in white, but my laptop (running Ubuntu 22.04) could not get IP address via DHCP. I manually set IP address, but I could not ssh to 192.168.1.1 or any other address in /24.
I tried pressing the reset button on the router, nothing changes no matter how long I press.
I read the failsafe wiki page, when turning on my router, my power LED never blinks. I don't know if it is in the failsafe state already, or bricked.
I was also trying to revert to the OEM firmware, but could not find any documentation on how to do this (given I could not see web GUI or ssh)
does anyone have similar issues? I am appreciated if you can help me fix this.
I was under the impression that the default gateway IP is 192.168.1.1 and the default allowed IP range is 1.x, not 0.x. Because the DHCP did not work, so I did not really know what was the correct default range.
I just tried to manually request IP from 192.168.0.x, and set router address to either 0.1 or 1.1, but neither allow me to ssh to the router.
Was R7900's wan port connected to the lan port of ISP' router or modem? If it was, disconnect it and power cycle R7900. Then try to access R7900 via 192.168.1.1.
I guess the router is busted like you said. I don't have experience with R7900 although I used to have a R7000 loaded with DD-Wrt (and recently converted a R6700 to R7000). It seems that you need the CFE TFTP + serial recovery method according to the OpenWrt R7900 Techdata. From my understanding, R7900 is a Costco's version of R8000 so you can ask Netgear or DD-Wrt (supports R8000) forums for how to recovery from a bricked R8000/R7900 too.
thank you so much @mechango, nmrpflash did the trick! I am happy that the router is finally working again.
it turns out timing is important for nmrpflash to work successfully - when turning on the router after launching the command, I first got an Timeout while waiting for TFTP_UL_REQ.
sudo nmrpflash -i enp2s0 -f R7900-V1.0.4.38_10.0.50.chk -T 20 -t 1000
Advertising NMRP server on enp2s0 ... /
Received configuration request from xx:xx:xx...
Sending configuration: 10.164.183.252/24.
Timeout while waiting for TFTP_UL_REQ.
however, immediately relaunching the command could allow the file to be uploaded. even thought I am still getting Timeout while waiting for 0000. error, the router was able to finish rebooting and function again
sudo nmrpflash -i enp2s0 -f R7900-V1.0.4.38_10.0.50.chk -T 20 -t 1000
Advertising NMRP server on enp2s0 ... -
Received TFTP_UL_REQ while waiting for CONF_REQ!
Received upload request without filename.
Uploading R7900-V1.0.4.38_10.0.50.chk ... OK
Waiting for remote to respond.
Timeout while waiting for 0000.
Good job. BTW, at which point I bricked my router was when I tried to flash an OpenWRT to get to finally flashing a Fresh Tomato firmware. It failed on the OpenWRT stage. Can anyone help in flashing the Tomato onto a r7900?