YazDHCP YazDHCP floods with dnsmasq errors

[SomeWhereOverTheRainBow]

In your output, both NVRAM vars are set to empty string.


I don't think you can install & run YazDHCP successfully unless it's in "Router Mode." Thanks for trying though.

I was sharing variables that is all. I know I couldn't install it.

Only a house has all features a human expects of a building to live in.
A shed, garage or extension have their own purposes and generally don’t come with a front porch, doorbell, bathroom and kitchen.

That depends on what you define a "front porch", "doorbell", "bathroom", and "kitchen" to be. In the DHCP static lease world, these terms have no meaning except for what you assign them to.

 

[Martinski]

OK, I have fixed the code & added a check in the export function to validate that the NVRAM entries being exported do not conflict with any existing DHCP IP address assignments that were added *after* the initial installation but *before* starting the "Export from NVRAM." This was necessary to avoid ending up with entries having the same MAC and/or IP addresses in the mix. However, this check is only for F/W 386.4 & later versions.

I've also added code to check that there are no conflicts between any NVRAM "dhcp_staticlist" entries (if set) and the DHCP client files data sent from the WebGUI page.

I'll submit a GitHub PR within the next ~20 minutes after I run a few more tests.

@Jack Yaz has merged the changes/fixes described above into the YazDHCP 'develop' branch.

For those who are having issues with the "duplicate dhcp-host IP address" messages, you can switch from the current master 1.0.5 version to the develop 1.0.6 version with the following command:

/jffs/scripts/YazDHCP develop

If you're already on the develop branch, update with the following command:

/jffs/scripts/YazDHCP forceupdate

Once updated successfully, you should see the "x. Export nvram to YazDHCP" menu option from the CLI if the NVRAM "dhcp_staticlist" variable is set to non-empty values. If so, run the export and then you can check if the "duplicate" messages are still coming from dnsmasq.

If you don't want to run the "export NVRAM" option, you can instead go to the YazDHCP webGUI page ("LAN - DHCP Server") and, without changing anything, simply click on the "Apply" button. This also triggers a check for MAC & IP address duplicates due to NVRAM settings.

 

[heysoundude]

AHA! THIS is what's filling up my jffs...(I've been too busy to poke about and find out myself)
I'll keep my eyes peeled for when Jack pushes this update.

 

[biohazardx9]

Bingo! was the culprit for me too. after a long while router would go nuts loose internet and act very strangely. upon reboot it would work for a few minutes then malfunction.
I guessed this was it as I didn't have any add-ons installed except yazwifi and yazdhcp.

 

[heysoundude]

well, these don't get too much attention/maintenance anymore from Jack or anybody else, so it might prove to be more a curse than a blessing to have them running sooner than later...

 

[Kingp1n]

So is it recommended to be running the development version of YAZDHCP versus the latest stable?

 

[Martinski]

So is it recommended to be running the development version of YAZDHCP versus the latest stable?

I'd say yes, but only if you want to have the latest fixes & additions that are currently in the 'develop' branch and are not yet merged into the 'master' branch.

 

[bennor]

So is it recommended to be running the development version of YAZDHCP versus the latest stable?

If YazDHCP master branch is running fine without any errors described previously, there isn't a need to update. "If it ain't broke, don't fix it" kind of thing. If you need or want the latest tweaks, enhancements, or fixes for specific issues then update to the develop branch.