Posted: Fri Oct 18, 2024 17:41 Post subject: DHCP Static Route broken by forbidden characters [Solved]
Router Model
Asus RT-AC5300
Firmware Version
DD-WRT v3.0-r58568 std (10/15/24)
Kernel Version
Linux 4.4.302-rt232-st56 #12481 SMP Tue Oct 15 05:05:13 +07 2024 armv7l
Posted: Sat Oct 19, 2024 2:24 Post subject: DHCP Static Route - Hostname only has alphanumeric and dash
I posted about the static route not working even after applying and rebooting the AC5300 and the PC using DHCP.
After 20 hours I checked and the static routes began working. Is DD-WRT designed to require some sort of time to pass to get DHCP static routes working?
[EDIT and SOLVED] I was wrong in this post because I was using forbidden characters in the
services/services/Static management/static leases/Hostname
As I was playing around with the fields I occasionally removed a forbidden character and it started working next time I check 20 hours later. This was lucky and unintentional. I edited all my entries copied from Merlin and ASUS firmware configurations (which allow forbidden characters) and fixed them by only using alphanumeric and dashes. DHCP now works!
I think this needs to be built into the router as a comment and added to the wiki for DHCP. Newcomers like me will not know this.
DNSMasq will not start if it has forbidden characters in static leases or wrong settings in additional DNSMasq options
or other wrong settings so check that also
I've also had this problem. I've been through my static leases and removed all '_' and '#' and replaced by '-'
and DHCP server is now 'Enabled - Running'.
But - can anyone definitively say what the 'forbidden characters'are exactly? It's very well to say 'no forbidden characters'
but how do we know what is allowed and what is forbidden? Thanks. Smile
It is underscores in hostnames which prevent DNSMasq from starting. Hyphens are ok.
Been there, seen that ...
Forbidden characters in DNS include any character that is not a letter (a-z, A-Z), digit (0-9), or hyphen (-)
Last edited by bootit on Wed Oct 23, 2024 8:03; edited 4 times in total
It's not clear from your description if you renewed the DHCP lease on your Windows machine (or rebooted it) after the change to the router. The fact it took nearly a full day strongly suggests it never did, and thus never knew of the static routes.