[
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.
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.
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:
EXAMPLES:
Rich (BB code):
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.
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:
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:
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
?
.
