Are you sure that you don't have invalid characters in your hostname that would result in dnsmasq failing to start? You only needed to obfuscate the MAC addresses, if anything, in your screenshot. Check your syslogs and ps to see if dnsmasq is running. You may have to "forget network" on your wireless clients as well.
If you're still on this build, it might be wise to update to current release (50357 at present) or wait, depending on the ongoing VPN development work:
Fedex03 wrote:
I start with a new build (DD-WRT v3.0-r49934 std (08/28/22)), reset the router and then I configured everytihng manually.
Are you sure that you don't have invalid characters in your hostname that would result in dnsmasq failing to start? You only needed to obfuscate the MAC addresses, if anything, in your screenshot. Check your syslogs and ps to see if dnsmasq is running. You may have to "forget network" on your wireless clients as well.
If you're still on this build, it might be wise to update to current release (50357 at present) or wait, depending on the ongoing VPN development work:
Fedex03 wrote:
I start with a new build (DD-WRT v3.0-r49934 std (08/28/22)), reset the router and then I configured everytihng manually.
I followerd your suggestion, and I enabled the Syslog.
I rebooted the router and I check the Syslog that reports:
Quote:
Oct 11 09:50:00 DD-WRT daemon.crit dnsmasq[2777]: bad DHCP host name at line 26 of /tmp/dnsmasq.conf
Oct 11 09:50:00 DD-WRT daemon.crit dnsmasq[2777]: FAILED to start up
I checked the dnsmasq.conf file and at line 26 I found that the host name is "*".
If I remember the "*", was allowed for the static leases. Am I right?
