YazDHCP YazDHCP - feature expansion of DHCP assignments (increasing limit on the number of DHCP reservations)

[-BH-]

Has anyone successfully enabled YazDHCP on the 3006.102.2 firmware? I have used this addon for years, and will be hard to live without it, but I cannot get the UI to work on the new firmware.

The install works as should, and the YazDCHP v1.0.6 version of the UI page is enabled in the router UI. Import from .csv seems to work per se - but no entries can be seen in the UI. List stays empty no matter what, but if I try to add one of the MAC addresses then the UI says it already exists. If I add something that is not in the list, it gets approved, but list still shows no entries.

 

[Tech9]

You have built-in Guest Network Pro in 3006 firmware. Not good for your intended use?

 

[-BH-]

Main issue for me is exporting and importing DCHP assignments. I have about 70 assignments currently and entering them manually every time there is a bigger update/equipment change is a drag..

 

[bennor]

The install works as should, and the YazDCHP v1.0.6 version of the UI page is enabled in the router UI.

Try using the develop version (1.0.7). Running the following two commands via SSH on the router to force update to YazDHCP 1.0.7.

/jffs/scripts/YazDHCP develop
/jffs/scripts/YazDHCP forceupdate

PS: There is some discussion of YazDHCP in the following discusson on the Asus-Merlin 3006.x firmware. See some of the comments, starting on page 2, by user Martinski who fixed several issues with develop version of YazDHCP 1.0.7:

Compatibility Findings with AddOns with GT-BE98 Pro

I am starting a thread to summarize my findings to date with my recently purchased GT-BE98 Pro (Merlin 3006.102.1_beta1 firmware) with the "traditional" add-ons. amtm v4.8: Works as designed, including swap file creation and entware installation. diversion v5.1.3: Works as designed, including...

www.snbforums.com

 

[Tech9]

Main issue for me is exporting and importing DCHP assignments.

My mistake, I was thinking about YazFi. You can't have DHCP reservations on the new Guest Network Pro anyway, AFAIK. The firmware evolves and some of the scripts you have used in the past don't apply anymore. Compatibility is not guaranteed either. You have to find new ways to achieve your goals.

 

[bennor]

My mistake, I was thinking about YazFi. You can't have DHCP reservations on the new Guest Network Pro anyway, AFAIK.

If I remember right when I played with the 3006 firmware on my RT-AX86U Pro you could set manual DHCP reservations for Guest Network Pro clients provided you didn't isolate Guest Network Pro from the main LAN. When intranet access was disabled Guest Network Pro would use a different IP address range (I want to say x.x.52.x or something like that). The inability to set manual reservations for IoT devices isolated from the main LAN was the main reason I went back to using Asus-Merlin and YazFi. I think I may have made a post about this at the time if I remember right.
Edit to add: Found my old post:
https://www.snbforums.com/threads/a...102_34312-2024-05-09.90015/page-5#post-909573

It appears you can manually set the Guest Network Pro WiFi client IP addresses on LAN > DHCP Server section provided you have "Use the same subnet as main network" enabled. When that option is disable the Guest Network Pro WiFi clients pull random IP addresses from the Gateway IP address network pool (in my testing of two Guest Network Pro custom networks they used 192.168.52.x for 5ghz network and 192.158.53.x for 2.4Ghz network). Did not see any way to manually set IP addresses for Guest Network Pro WiFi clients when "Use the same subnet as main network" is disabled. That may be a problem for some who want more granular control like they can get with Asus-Merlin and YazFi's custom scripting to set Guest Network WiFi IP addresses.

 

[-BH-]

Try using the develop version (1.0.7). Running the following two commands via SSH on the router to force update to YazDHCP 1.0.7.

/jffs/scripts/YazDHCP develop
/jffs/scripts/YazDHCP forceupdate

PS: There is some discussion of YazDHCP in the following discusson on the Asus-Merlin 3006.x firmware. See some of the comments, starting on page 2, by user Martinski who fixed several issues with develop version of YazDHCP 1.0.7:

Compatibility Findings with AddOns with GT-BE98 Pro

I am starting a thread to summarize my findings to date with my recently purchased GT-BE98 Pro (Merlin 3006.102.1_beta1 firmware) with the "traditional" add-ons. amtm v4.8: Works as designed, including swap file creation and entware installation. diversion v5.1.3: Works as designed, including...

www.snbforums.com

Thanks. That did the trick - some incompatibilities with images apparently still, but now at least the device list is visible!

 

[pgershon]

I am having an issue with a series of old IP addresses that had been statically assigned (but now released) remaining reserved in DHCP. I found the entries that reserve the IPs in the dnsmasq.conf file, but i realize that editing the lines out of the dnsmasq.conf is not a good fix as they will come back after a reboot. I found some instructions in this thread (near page 1) that talked about modifying files in jffs/addons/YazDHCP.d but I do not see those files there (staring with .). I only see Advanced_DHCP_Content.asp, CustomUserIconsConfig, DHCP_Lease, DHCP_clients and DHCP_clients.bak. I am using YazDHCP 1.0.7. How can I more permanently modify the dnsmasq.conf to remove these dated entries that should not be there? Essentially I have 7 reservations for devices no longer on my network or that now have a different static IP.

 

[bennor]

@pgershon, what program are you using to access the router using SSH and view the jffs/addons/YazDHCP.d directory? Check that program to ensure it shows the three hidden files; .hostnames, .staticlist, .optionslist. You may have to issue the following command in the SSH terminal window to list the hidden files: ls -a
Example using Putty:

If using Windows, try using WinSCP (https://winscp.net/eng/index.php) to access the router via SSH. It should graphically show the three hidden files.
Example using WinSCP:

To confirm, you did remove the reserved manual entries in question from the router's GUI's Advanced Settings > LAN > DHCP Server > Manually Assigned IP addresses in the DHCP scope?
(post edited to add image)

 

[pgershon]

Thanks. I found the three files. But I did not solve my issues. The three Yaz files look like they should based on my settings. But the dnsmasq.conf file itself has an old list of IP address assignments for former static IP clients no longer on my network. How can I clear these entries so I can reuse the IP numbers?

I edited the dnsmasq.conf but after rebooting the machine, those entries all returned. Something that is very clearly not in the YAZ files is instructing my router to put these old addresses back in the dnsmasq.conf. It is not in the dnsmasq.conf.add file (which contains the names of the Yaz files). Any ideas where to look? Short of a clean reset of the router, which is a last resort. If I had to guess, I did something previously without do ing a clean wipe of the router and that caused this situation. Here is the dnsmasq.conf file. I have no idea what is populating those "dhcp-host=" lines.

pid-file=/var/run/dnsmasq.pid
user=nobody
bind-dynamic
interface=br0
interface=pptp*
no-dhcp-interface=pptp*
no-resolv
servers-file=/tmp/resolv.dnsmasq
no-poll
no-negcache
cache-size=1500
min-port=4096
dns-forward-max=1500
bogus-priv
domain-needed
dhcp-range=lan,192.168.1.121,192.168.1.170,255.255.255.0,86400s
dhcp-option=lan,3,192.168.1.1
dhcp-option=lan,252,"\n"
dhcp-authoritative
interface=br1
dhcp-range=br1,192.168.101.2,192.168.101.254,255.255.255.0,86400s
dhcp-option=br1,3,192.168.101.1
interface=br2
dhcp-range=br2,192.168.102.2,192.168.102.254,255.255.255.0,86400s
dhcp-option=br2,3,192.168.102.1
dhcp-host=10D:B11:2C:2E,set:10D:B11:2C:2E,192.168.1.19
dhcp-host=44:17:93:A3:FC:40,set:44:17:93:A3:FC:40,192.168.1.196
dhcp-host=A8:03:2A:BD:48:4C,set:A8:03:2A:BD:48:4C,192.168.1.193
dhcp-host=A8:03:2A:BA:4F:74,set:A8:03:2A:BA:4F:74,192.168.1.194
dhcp-host=B4:8A:0A:1C:A0:B4,set:B4:8A:0A:1C:A0:B4,192.168.1.187
dhcp-host=A8:03:2A:BC:91C,set:A8:03:2A:BC:91C,192.168.1.192
dhcp-host=9C:3E:53:17:F4:26,set:9C:3E:53:17:F4:26,192.168.1.25
dhcp-host=B4:B0:24:3A:6A:E1,set:B4:B0:24:3A:6A:E1,192.168.1.190
dhcp-host=D4:8D:26:52:57:90,set4:8D:26:52:57:90,192.168.1.99
quiet-dhcp
quiet-dhcp6
dhcp-name-match=set:wpad-ignore,wpad
dhcp-ignore-names=tag:wpad-ignore
dhcp-script=/sbin/dhcpc_lease
script-arp
edns-packet-max=1232

dhcp-hostsfile=/jffs/addons/YazDHCP.d/.staticlist # YazDHCP_staticlist

 

[bennor]

It may help if you post dnsmasq.conf (or the portion of it showing the IP addresses), redacting sensitive information.

It may help to check if there are custom clients saved to NVRAM. If so maybe removing them will clear your issue (or maybe not). Run the following command via SSH to see if there are any NVRAM custom client entries.
nvram get custom_clientlist
One possible way to remove all custom client entries is by running the following command via SSH.

nvram set custom_clientlist=""
nvram commit

Note: One uses the commands to clear NVRAM values at their own risk!!!

 

[pgershon]

Thanks again.

I posted the above as an edit after I initially posted, but here is the critical part:

dhcp-host=10D:B11:2C:2E,set:10D:B11:2C:2E,192.168.1.19
dhcp-host=44:17:93:A3:FC:40,set:44:17:93:A3:FC:40,192.168.1.196
dhcp-host=A8:03:2A:BD:48:4C,set:A8:03:2A:BD:48:4C,192.168.1.193
dhcp-host=A8:03:2A:BA:4F:74,set:A8:03:2A:BA:4F:74,192.168.1.194
dhcp-host=B4:8A:0A:1C:A0:B4,set:B4:8A:0A:1C:A0:B4,192.168.1.187
dhcp-host=A8:03:2A:BC:91C,set:A8:03:2A:BC:91C,192.168.1.192
dhcp-host=9C:3E:53:17:F4:26,set:9C:3E:53:17:F4:26,192.168.1.25
dhcp-host=B4:B0:24:3A:6A:E1,set:B4:B0:24:3A:6A:E1,192.168.1.190
dhcp-host=D4:8D:26:52:57:90,set4:8D:26:52:57:90,192.168.1.99

I also confirmed that the offending IPs items are not in the NVRAM client list that you had me look at. They are coming in from somewhere else.

 

[bennor]

Not sure if you answered the question, but have the IP addresses at issue been removed from the Advanced Settings > LAN > DHCP Server > Manually Assigned IP addresses in the DHCP scope section and the router along with client network devices rebooted?

Are you running any other addon scripts?

 

[pgershon]

1) Yes, the IP addresses at issue are all 100% removed from Advanced Settings > LAN > DHCP Server > Manually Assigned IP addresses. I have tried putting them in there and the linked devices do not get assigned the IP. So I removed.
2) The devices now have different static IP addresses that they are functioning perfectly with. The devices were rebooted. Most of them are Shelly NG relays, FWIW.
3) I do not believe I am running any other add-on scripts. If I am, I should not be. How can I check for 100% sure?

 

[pgershon]

Thanks again.

I posted the above as an edit after I initially posted, but here is the critical part:

dhcp-host=10D:B11:2C:2E,set:10D:B11:2C:2E,192.168.1.19
dhcp-host=44:17:93:A3:FC:40,set:44:17:93:A3:FC:40,192.168.1.196
dhcp-host=A8:03:2A:BD:48:4C,set:A8:03:2A:BD:48:4C,192.168.1.193
dhcp-host=A8:03:2A:BA:4F:74,set:A8:03:2A:BA:4F:74,192.168.1.194
dhcp-host=B4:8A:0A:1C:A0:B4,set:B4:8A:0A:1C:A0:B4,192.168.1.187
dhcp-host=A8:03:2A:BC:91C,set:A8:03:2A:BC:91C,192.168.1.192
dhcp-host=9C:3E:53:17:F4:26,set:9C:3E:53:17:F4:26,192.168.1.25
dhcp-host=B4:B0:24:3A:6A:E1,set:B4:B0:24:3A:6A:E1,192.168.1.190
dhcp-host=D4:8D:26:52:57:90,set4:8D:26:52:57:90,192.168.1.99

I also confirmed that the offending IPs items are not in the NVRAM client list that you had me look at. They are coming in from somewhere else.

These are my addons:
YazDHCP.d amtm custom_settings.txt diversion shared-jy vpnmgr.d

 

[pgershon]

I found the problem. NVRAM dhcp_staticlist had all the bad IPs. nvram set dhcp_staticlist="" fixed it