YazDHCP YazDHCP v1.2.1 [2025-Oct-25] - Feature expansion of DHCP assignments (increasing limit on the number of DHCP reservations)

[Martinski]

...
Attached is the System Log( I believe ) - I removed any MACs and External IPs and Other sensetive data was changed to protect the innocent!!!

While reviewing your syslog file, I noticed that you have quite a lot of the following entries:

... router dropbear[1517293]: Login attempt for nonexistent user from ....

I counted 58 such entries within the ~16 hours that your log covered. All indications are that all those attempts failed, so this is just an FYI in case you didn't know. I suggest making sure your SSH server is not accessible over WAN; but if that's how you want it, I'd strongly recommend disabling Password Login, changing the default SSH port, and using *only* strong SSH keys.

Just my 2 cents.

 

[Martinski]

Just trying to fold in one other person who is not seeing the same results as bennor and I, would your advice (above) also apply to CaptainSTX issue regarding YazDHCP in that linked thread please?

I don't know since that user has not provided enough details and context for the problem, but it wouldn't hurt to run the very latest 'develop' branch version, and if the same problem continues, then provide clear screenshots and more details/context as the other 2 users have done.

 

[Reef2009]

If you have the time, I'd suggest running the latest YazDHCP 'develop' branch v1.2.1 version. See post #117.

YazDHCP - YazDHCP v1.2.0 [2025-Oct-12] - Feature expansion of DHCP assignments (increasing limit on the number of DHCP reservations)

Good news. Ok I don’t use YazFi; IIRC it’s not supported atm? Would you be open to uninstalling it and looking at the outcome? ie simplify it down to YazDHCP?

www.snbforums.com

If you continue to get YazDHCP errors in the syslog *after* installing the latest v1.2.1 version and resetting the DHCP IP address assignments, would you please provide a copy of your /jffs/addons/YazDHCP.d/.staticlist file via DM?

You can redact the MAC addresses by obscuring only the first 3 hex values (e.g. XX:XX:XX:AB:CD:FF).
Also, please provide clear screenshots of your "LAN IP Address" and "Subnet Mask" settings.

no good results / fix.
the requested export and screenshots are in your DM

 

[peepsnet1]

Didnt work for me either!!

DMed info

 

[Martinski]

Thanks to a debug log provided by @Reef2009, I was able to find and fix the bug that was causing the malformed dnsmasq directives, such as the following:

set:lan
br1,XX:XX:XX:AA:BB:CC,set:XX:XX:XX:AA:BB:CC,192.168.1.2,HostName

The fix is now available in the latest 'develop' branch v1.2.1 version [ v1.2.1_25102001 ]

 

[peepsnet1]

OK... What if I told you:
I woke up this morning and had a few devices that were not connected and they were because an AIMesh was not connnected... So I rebooted my Router and it all began working on 1.2.1!!!

 

[peepsnet1]

OK... I updated YazDHCP with "develop" just before rebooting and at the same time you posted this message...
That is what happened...

It works now!!

I rebooted and all my reservations were assigned correctly... At least to my Main Group. I do not have any guest assignments...

 

[peepsnet1]

Now I cannot login to the webUI...

This page shows up...

I enter my UN / PW and click Sign In. Then This...
Cleared Cache, tried different browsers, icongnito mode...

Reinstalling 1.0.10 and rebooting corrected the issue!!!!

Any Ideas??

 

[peepsnet1]

Ok... Sorry...

It appears the WebUI is going up and down every few seconds... I don't know what this is now...
I thought it was working but now I cannot get into my router at all... ill have to restore from a backupmon... Damn!!

I have to go to work so it will be tomorrow before I can report back

 

[jksmurf]

Ok... Sorry...

It appears the WebUI is going up and down every few seconds... I don't know what this is now...
I thought it was working but now I cannot get into my router at all... ill have to restore from a backupmon... Damn!!

I have to go to work so it will be tomorrow before I can report back

Amazon Web Services hit... ?

 

[bennor]

It appears the WebUI is going up and down every few seconds... I don't know what this is now...

If you have SSH enabled on the router, SSH into the router to see if it can be accessed. One can then run top via ssh to see if that might provide a clue as to what the services are doing.

 

[peepsnet1]

If you have SSH enabled on the router, SSH into the router to see if it can be accessed. One can then run top via ssh to see if that might provide a clue as to what the services are doing.

I just restored the router because I had to go to work and I needed my internet up for the family.

But I still did have SSH access and I considered topping it to take a look and see what was going on.

But at least I'm back to a known good state and to continue to debug the YazDHCP script.

 

[Reef2009]

Thnx @Martinski the fixed worked.
But I needed to uninstalled, reboot, reinstalled, Developer reboot, import DHCP Clients and ofcource with finalnreboot.
Thnx for your support!

 

[RMerlin]

It appears the WebUI is going up and down every few seconds... I don't know what this is now..

Known issue with 388.10 and people using either Home Assistant or the mobile application. Disconnect either of these from the router for now.

 

[peepsnet1]

Known issue with 388.10 and people using either Home Assistant or the mobile application. Disconnect either of these from the router for now.

Good to know... I'll drop the connection from both!

 

[peepsnet1]

Well... My login issues seem to have goin away with the above help.

And YazDHCP 1.2.1 seems to work then!!

I'll post more if I have issues.

 

[CaptainSTX]

[CONTINUATION from previous post]

8) The menu option to toggle the new functionality will be grayed out and marked as UNAVAILABLE if there are no enabled Guest Networks whose subnet is separate from the main LAN subnet.

View attachment 68326

9) Whenever the YazDHCP WebUI page is loaded, you will see an 8-to-10 sec. "loading" delay due to the JavaScript call to the shell script requesting a check-and-validation status of each client entry, so the script executes code to validate all the existing client IP address assignments against all the Guest Networks profiles currently found enabled (or possibly disabled), to make sure that the associated virtual interfaces have been identified, and the appropriate dnsmasq directives have been issued to the correct dnsmasq instance associated with each Guest Network.

----------
*NOTE*:
----------
YazDHCP will *not* export or transfer any IP address reservations found in user-supplied custom files (e.g. /jffs/configs/dnsmasq*.conf.add) into its internal files. Only NVRAM-based DHCP settings are checked and transferred.

View attachment 68329

The reason is that, unlike the built-in NVRAM key-value pairs, the format of the dnsmasq directives found in user-supplied custom files is not fixed and consistent, so it can vary widely because the order of the parameters in the dnsmasq directive lines is essentially "free form."

So if you have created such custom files, you basically have 3 choices to transfer your current IP address assignments to YazDHCP:

a) Manually transfer the IP address assignments into NVRAM by inputting them into the corresponding WebUI page for each Guest Network profile. Once this is completed, you can use the SSH CLI 'x' menu option to trigger the export process.

b) Manually transfer the IP address assignments directly into the YazDHCP internal CSV-formatted client list (/jffs/addons/YazDHCP.d/DHCP_clients) by following the required format shown below:

MAC,IP,HOSTNAME,DNS

EXAMPLES:

MAC,IP,HOSTNAME,DNS
AA:BB:CC:DD:EE:FF,192.168.50.10,,
AB:BC:CD:DE:EF:FA,192.168.50.11,MyHostName1,
FF:EE:DD:CC:BB:AA,192.168.50.12,MyHostName2,9.9.9.9

Once you have finished adding all the entries into the internal client list file, you can use the SSH CLI '1' menu option to process the newly-modified list.

View attachment 68327

c) If you prefer making the above changes offline on your personal laptop using your favorite text editor, or perhaps using MS Excel, you could export to CSV your current client list using the WebUI:

View attachment 68328

Then manually add your IP address reservations to the CSV file. After you have finished making all the changes and additions, you can then import the modified file back into YazDHCP using the WebUI page. Once you're satisfied with all your changes, make sure to click on the "Apply" button to make them persistent.

Also, it's very important to make sure you remove all IP address reservations from your custom files that have been transferred to YazDHCP to prevent dnsmasq from getting duplicate entries/directives, which is bound to cause some issues when restarting the dnsmasq process.



** The fork from @Jack Yaz's YazDHCP add-on is now hosted on the AMTM-OSR GitHub repo:

GitHub - AMTM-OSR/YazDHCP: Feature expansion of DHCP assignments using AsusWRT-Merlin's Addons API to read and write DHCP assignments, increasing the limit on the number of reservations.

Feature expansion of DHCP assignments using AsusWRT-Merlin's Addons API to read and write DHCP assignments, increasing the limit on the number of reservations. - AMTM-OSR/YazDHCP

github.com

In my case your solution was the simplest and worked. I simply added the two devices that are in the 53 VLAN to the CVS file and then imported back onto the router and they now show up on the DHCP server list with the correct color. Problem solved. Thanks for the suggestion.

 

[jksmurf]

In my case your solution was the simplest and worked. I simply added the two devices that are in the 53 VLAN to the CVS file and then imported back onto the router and they now show up on the DHCP server list with the correct color. Problem solved. Thanks for the suggestion.

Super pleased you got this going, was starting to worry about a glitch.

I did make a very similar suggestion on Sunday but I think it got lost in all the traffic . Ultimately you got a result, which is what matters.

I’m not sure what to suggest, apart from an uninstall / reinstall, check your csv file has all the 53 subnet entries and add them manually if needed, reimport.

 

[bennor]

I did make a very similar suggestion on Sunday but I think it got lost in all the traffic .

As did I in the post following yours in that discussion, which included a mention of paying attention the Note section of the [CONTINUATION from previous post]. With so much back and forth it was easy for the suggestions or information to be lost or discounted.

Edit to add: If you are not seeing the BR53 VLAN manually reserved IP addresses on the LAN > DHCP Server > Manually Assigned IP addresses in the DHCP scope section, that likely means they were not entered properly into the correct YazDHCP file (or exported YazDHCP cvs file, then imported into YazDHCP) or were not correctly pulled from the NVRAM. Did you follow all the steps detailed in the YazDHCP v1.2.0 directions? See the following two links, particularly the "note" information in the second link:
https://www.snbforums.com/threads/y...of-dhcp-reservations.94827/page-4#post-971788
https://www.snbforums.com/threads/y...of-dhcp-reservations.94827/page-4#post-971789

 

[Martinski]

Release Notes for YazDHCP v1.2.1 production version now available
[2025-Oct-25]

1) FIXED: Bug when extracting and setting the dnsmasq directive interface tag.
2) IMPROVED: Modified code to handle scenarios where the subnet mask goes beyond the standard "255.255.255.0" default setting.
3) Miscellaneous code improvements.

Documentation for the "Allow Guest Network Client DHCP IP Address Reservations" feature has now been added to the README file on the GitHub repository for future reference:

YazDHCP/README.md at master · AMTM-OSR/YazDHCP

Feature expansion of DHCP assignments using AsusWRT-Merlin's Addons API to read and write DHCP assignments, increasing the limit on the number of reservations. - AMTM-OSR/YazDHCP

github.com