First thing I did was: reset to defaults in the DD-WRT GUI), upgrade to 44627 which seems to be the latest from today (@egc mentioned 44628 but couldn't find that), then telneted in and ran nvram erase && reboot.
That didn't work, so I reverted back to stock by uploading stock Netgear firmware (should I have just hit "reset"?). Then tried installing the stock to DD-WRT chk firmware, and reinstalled 44627.
Last edited by pbc on Sat Oct 24, 2020 17:40; edited 1 time in total
This is the first time I have heard of this issue.
The best I can tell you is revert to your last known working build and config.
Pretty sure this has nothing to do with your static leases.
This is the first time I have heard of this issue.
The best I can tell you is revert to your last known working build and config.
Pretty sure this has nothing to do with your static leases.
44627 shows up as 44628 on some of my routers.
Just another DD-WRT inconsistency
I don't have a last known working build unfortunately. I reverted back to Stock firmware years ago during the Kong Build days.
Literally just pulled this router out of the closet (have two R7000s, one that I leave on stock firmware) as I wanted to go back to DD-WRT.
This is such an odd issue. Does this router have two partitions like some of the Linksys routers? Maybe I messed up somewhere in the install?
Wow, heck of a find. I'm pretty sure I used that firmware some time ago. Will have a look at the thread and see if I can figure things out (have to pause for a bit as my son came home and apparently his PS4 takes precedent).
I used telnet (in putty) and I entered these commands one at a time. The CFE is in the mtd0 folder.
mtd unlock mtd0
mtd write -f /tmp/stock-cfe.bin mtd0
erase nvram
reboot
Finally update to current version and do a reset to factory defaults.
This worked for me, default username and passwords for Winscp and Putty logins were both root then the password for the router that you have set.
It took me a little while to realize the easiest way to actually get the CFE files into the tmp folder on router, but once that was clear it was all quite simple.
Good luck!
BTW, when you see that SSH is greyed out in the administration section, you need to go to services and enable Secure Shell.
Copy these to the Additional DNSMasg options and Bob's your uncle
Note: only letters and numbers in the name and a hyphen or underscore, new versions strictly adhere to the allowed characters.
Non allowed characters will crash DNSMasq
Now that I have that other issue "resolved"...so I copied and pasted my reservations into DNSMasg options.
Instead of putting 1440m, can I simply leave it as:
Copy these to the Additional DNSMasg options and Bob's your uncle
Note: only letters and numbers in the name and a hyphen or underscore, new versions strictly adhere to the allowed characters.
Non allowed characters will crash DNSMasq
Now that I have that other issue "resolved"...so I copied and pasted my reservations into DNSMasg options.
Instead of putting 1440m, can I simply leave it as:
Using your examples above so that it doesn't limit the reservation?
The static leases are delimited by '=' characters and each lease is separated by a space. The '=' at the end in the last position is for the lease time. If empty, it is static. For example:
Code:
00:11:22:33:44:55=7000-BR=192.168.1.2=
vs.
Code:
00:11:22:33:44:55=7000-BR=192.168.1.2=1440
Follow redhawk0's post:
redhawk0 wrote:
You might want to try adding your Static leases back in from a command line. I have about 25 myself...so this is how I do it when I reset.
Here is an example with just 2 static leases.
redhawk
Code:
nvram set static_leasenum="2"
nvram set static_leases="00:11:22:33:44:55=7000-BR=192.168.1.2= 66:77:88:99:AA:BB=6300v2-BR=192.168.1.3= "
Copy these to the Additional DNSMasg options and Bob's your uncle
Note: only letters and numbers in the name and a hyphen or underscore, new versions strictly adhere to the allowed characters.
Non allowed characters will crash DNSMasq
Now that I have that other issue "resolved"...so I copied and pasted my reservations into DNSMasg options.
Instead of putting 1440m, can I simply leave it as: