Router/Version: Netgear R7200
File/Kernel: ddwrt 04-20-2026-r64533 (4/20/2026)
No prior reset
AP Mode
Issues: see below (no WAN connection until update flash with r7200_webflash.bin, docs issues, displayed hw version after initial flash wrong).
Again, am a newb so please excuse if this is bad format or in wrong HW board, though I believe by briefly checking this is the correct one. I did manage to eventually get everything working and in quite quick order. These are all minor issues; just thought someone should know.
Issues:
1. Wiki displays typo'd folder path for the r7200 model firmware image location. Wiki under "Firmware image locations" shows a bulletpoint for r7200 is missing (see image attached), the bulletpoint says r6900v2 can be found under /r7200 folder path. The true folder path on the beta FTP server is actually r7200 (https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2026/04-20-2026-r64533/netgear-r7200/). I would have submitted a docs change myself but the rules here seem pretty strict.
2. There is no WAN connection (even after modem power cycle) AFTER flashing the factory-to-ddwrt.img file but BEFORE updating with r7200-webflash.bin. Using only the factory-to-ddwrt.img flash, the router model also displays an unknown router on the main page, r6200, not r7200. I am unsure if this is the intended behavior, but it would be clearer on the docs page for this router if there was a warning that said Router will not work unless updated with the r7200-webflash.bin file.
3. Assorted docs details which might be helpful.
(a)The original firmware that came on the router (some netgear trash) makes it extremely hard to connect to the router interface if the router is connected to WAN. Therefore you can't upload the factory-to-ddwrt.img file easily. A useful docs update would be under Procedure as a first step: 'Ensure the router with factory firmware is NOT connected to WAN before or during upgrade to DD-WRT.'
(b) Also, the firmware flash does work wirelessly, which I had to do since the factory firmware wouldn't let me connect with an static ip/ethernet as per the 1st step of Procedure in the Wiki. I assume wireless is not the preferred method in general for DD-WRT but it was necessary in my case with this router and may be necessary for others.
Screenshot 2026-04-21 at 23-44-54 Netgear Nighthawk AC2100 - DD-WRT Wiki.png
Description:
Firmware bulletpoint for R7200 seems to be typo'd as a second R6900v2.
Joined: 08 May 2018 Posts: 17296 Location: Texas, USA
Posted: Wed Apr 22, 2026 17:12 Post subject:
We do not use direct links for any files in the Wiki except for certain devices of yore. Sounds like your upstream router is 192.168.1.x and Netgear Genie chose another subnet, possibly in 10.x.x.x, but this is also why when you set static IP you do it correctly after checking client IP and also why you can use routerlogin.net if the static IP is set correctly with gateway. Typo will be corrected and note added shortly, even though it's always been a given to only have the client PC connected when flashing. And it doesn't seem as if you did a reset after flashing factory-to-ddwrt.img, but I guess I do need to add a note about double-tap flash being required. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... RSS feed for DD-WRT releases (2025) RSS feed for DD-WRT releases (2024) RSS feed for DD-WRT releases (2023)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
I see the docs have been updated. Thank you for the quick response and attention. Was just hoping to save others some trouble for this particular router.
Re: inability to connect via ethernet
kernel-panic69 wrote:
Sounds like your upstream router is 192.168.1.x and Netgear Genie chose another subnet, possibly in 10.x.x.x, but this is also why when you set static IP you do it correctly after checking client IP and also why you can use routerlogin.net if the static IP is set correctly with gateway.
That sounds about right, now that I think about it. However I was pretty sure I did do it correctly according to the wiki but because of the default subnet, it didn't connect. Maybe I misunderstood something.
kernel-panic69 wrote:
Typo will be corrected and note added shortly, even though it's always been a given to only have the client PC connected when flashing.
That makes sense. Thank you for adding the note under point 1 on the wiki.
It was not super clear to me that it was a given only the client PC can be connected during the entire procedure. I had the WAN port connected (using default NG firmware) to test the hardware before resetting and flashing, since it was new router, and it wasnt obvious to disconnect it before starting the flash. Again, I'm newbie.
For anyone reading this in the future: It is possible that with the default firmware that after initial NetGearGenie setup, if you are connected to WAN it will lock you out of the router interface behind a faulty "Make a NetGear Account" page.
The only way I found to resolve this was to reset the router, go through initial NGGenie setup again, and then disconnect the wan port and NOT exit the NetGear WebUI. Then flash DD-WRT as per the instructions.
