HAP AC3 Does not properly extend Network DHCP Address when expanding from /28(13hosts) to /27(29hosts)

[aa3jc]

Originally, about a year ago, I had setup my AC3’s Network settings for /28(13hosts), but 2 days ago I changed it to /27(29hosts). As expected, the network Mesh address along with the LAN address, and DHCP range followed the new IP scheme and assigned the range to follow with 29 DHCP Addresses, again as expected.

Currently running the latest nightly firmware version: 20260303-6030f5e9

Now, only 10 DHCP address will assign, and even though it shows the full 29 addresses, it will not assign 2 of the original devices connected, nor anything else new. Only 8 addresses are being assigned. The other two show connection and activity, but will not showup in the "Local" or can be accessed via any of the remaining DHCP addresses. Any new devices added show no connection via ethernet, yet if I remove the ethernet from the HAP and connect it to my main router within seconds the lan device receives a DHCP address and is accessable via that address.

I attempted to reset the DHCP to assign /28(13hosts) and after a reboot only 10 devices (same as above) would work correctly, and the original two displayed the same behavior as above.

Support Data and screen shots attached!

supportdata-AA3JC-AC3-HTFLD-LAN-2026-3-19-15-20.tar.gz

AA3JC-AC3-HTFLD-LAN-Main Status Page.pdf

AA3JC-AC3-HTFLD-LAN-DHCP Page.pdf

[aa3jc]

Another issue found, I was able to change the AC3 to /27(29hosts) and the AC3 seems to have reserved the 29 IP addresses. (See attachments) Issue now found the AC3 will only assign 10 addresses, even though there are 15 devices connected to the HAP through a dumb switch.
If I unplug the ethernet cable from the HAP to the switch and plug it into a diffrent node that is setup for /28(13hosts) all the devices receive IP addresses without any problem. When reconnected back to the HAP maximum of 10 IP address are handed out leaving the rest without IP addresses.

[aanon4]

Looking at the DHCP configuration, this is the relevant configuration line for 'dnsmasq':

dhcp-range=set:lan,10.233.186.226,10.233.186.254,255.255.255.224,1h

which looks to be correct unless I'm missing something. It would be interesting to see a copy of /tmp/dhcp.leases from this node - it's not part of the support data.

[aa3jc]

I have tried every method I know, changing the node ip address, the DHCP size, and nothing will allow 27 hosts. As requested, please find a copy of /tmp/dhcp.leases

[aanon4]

I notice that the IP address of the mesh is 10.55.92.1, which is the same as the IP address of the LAN 10.55.92.1 - not sure why, but not a good thing. The mesh address is the easiest to change from the UI. Try making it 10.54.92.1 (for example).

[aa3jc]

Change made. I left it that way after my testing as it didn't make any diffrence either way!

[aanon4]

At this point perhaps you can email me a password to this node - might be easier.

[aa3jc]

Tim, Password for:   http://aa3jc-ac3-htfld-lan.local.mesh/a/status   password:  12345! Joe Joe Caltabiano-AA3JC PEMA-ACS Eastern Area Section Chief

…

________________________________________________ Joe Caltabiano AA3JC ComL, ComT, Auxcom, ACS Eastern Area PEMA-ACS Section Chief 215-237-7991 (cell) MCAR Mesh IP Phone: 215-3103 PEMA-ACS Mesh IP Phone: 215-2001 HOIP: 100294 Amateurwire:  2233 ***@***.*** ***@***.*** ***@***.*** Apr 20, 2026 7:45:42 PM Tim Wilkinson ***@***.***>:

[Image]*aanon4* left a comment (aredn/aredn#2650)[#2650 (comment)] At this point perhaps you can email me a password to this node - might be easier. — Reply to this email directly, view it on GitHub[#2650?email_source=notifications&email_token=ASMLSFZUFZM6MCIZOBK5BHL4W2ZCLA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRYGQ4TMOBYHAYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4284968880], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ASMLSF7YPPYY4WW5QYR36W34W2ZCLAVCNFSM6AAAAACWYRUDR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEOBUHE3DQOBYGA]. You are receiving this because you authored the thread. [Tracking image][https://github.com/notifications/beacon/ASMLSF75GPWAZQOA4UIVAHT4W2ZCLBFCNFSM6AAAAACWYRUDR2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTX7M5X3BJTSMVQXG33OUZQXK5DIN5ZA.gif]