[jsmiddleton4]

I'm not a Linux_router_code guy so I can't get beyond reporting symptoms. I have no idea about causes.

I also realize this kind of thing is not a big deal, not a high priority thing.

But DNSMasq and the GUI reporting part of the firmware is messed up. I can duplicate the symptoms easily.

In the Status section where we are supposed to be able to see and manage dhcp leases if I use DNSMasq sometimes that lease information isn't even reported.

I thought it was only when I used JIFFS to store the dhcp database. Not so.

DNSMasq does seem to "work" in the sense my clients get their dhcp reserved IP's. However I've noticed sometimes despite having google dns ip's in the DNSMasq configuration some times clients do not get the 8.8.8.8, etc., but instead have my cable isp provider's dns ip information.

It is as if the DNSMasq module shut down. Again not a code guy so I am in no way certain about causes.

When bypassing DNSMasq, turning it off completely, clients report the Google dns, Status LAN reports correctly, etc.

Something between the FW and DNSMasq is not playing well with others.

I've rebooted after changing settings, refreshed clients, etc. I'm confident that the symptoms I'm seeing is as I've reported something going on in the interplay between DNSMasq and the FW.

I've also noticed pages load, web sites resolve, etc., just a bit faster if I don't use DNSMasq. I have no way to objectify that. But it is the case.

[crashfly]

First of all, you have not reported what kind of router you are using.

Secondly, you need to specify the revision of the firmware you are using. (Use numbers not the date.)

Because, with out this information, the most people can do for you is recommend you to read the "Peacock" thread so solutions and quite possibly update your firmware to something more recent.

[jsmiddleton4]

My bad and I was just thinking about what I left out as well.

But it is in my signature.

I'm not expecting anyone to "fix it". I've banged on it enough to know it is something Kong or Brainslayer once stuff of higher priority get addressed need to take a look at.

Netgear R7000
Kong 23435 OLD

uDHCP and setting the DNS server address to the router in setup works fine.

[jsmiddleton4]

Tried blasting nvram, erase nvram via telnet, loaded the NEW driver and started over. Same experience.

Once I get to 12 dhcp reserved IP's DNSMasq quits working.

Disable it and everything is fine.

[jsmiddleton4]

Left DNSMasq disabled over night. Used the FW's default and uDHCP.

Just for kicks I tried one more time enabling DNSMasq this morning. This kind of thing can drive me nuts. So I wanted to try one more time.

Everything worked. Did the DNSMasq app need time to clear its information?

I don't get why it works this morning.

[jsmiddleton4]

Left DNSMasq disabled over night. Used the FW's default and uDHCP.

Just for kicks I tried one more time enabling DNSMasq this morning. This kind of thing can drive me nuts. So I wanted to try one more time.

Everything worked. Did the DNSMasq app need time to clear its information?

I don't get why it works this morning.