This has been a somewhat re-occuring issue for quite some while, but I may have noticed something consistent.
Off and on for several years, I have had devices connected to LAN ports of either of my hAP nodes that have DHCP reservations, but the reservation was not honored, and some other address was assigned. Have not seen that for a while, but after a bunch of re-arranging here, I noticed the problem showing up on both hAPs with multiple devices. This morning I noticed a consistency. Every device that was getting a wrong address, under DHCP leases in the hAP was showing the hostname as being the IP address that it should have had based on a DHCP reservation and the Current DHCP Lease showing the assigned address and MAC. Unfortunately I did not screen capture this condition. The part that was consistent was that EVERY device that had the Do Not Propagate checkbox selected was in this incorrect state. I unselected the DNP box on one device and saved it in the hAP and then on the device (a router in the first case) I released and renewed the DHCP client and promptly got the correct address based on the DHCP reservation. I repeated the test on several other devices, with the same results. As soon as I unselected DNP and renewed the lease, the hAP assigned the correct address based on the DHCP reservation. Re-selecting the DNP checkbox and renewing the lease did not immediately result in an incorrect IP address being assigned.
Both of my hAPs are currently running 3.22.6.0
Off and on for several years, I have had devices connected to LAN ports of either of my hAP nodes that have DHCP reservations, but the reservation was not honored, and some other address was assigned. Have not seen that for a while, but after a bunch of re-arranging here, I noticed the problem showing up on both hAPs with multiple devices. This morning I noticed a consistency. Every device that was getting a wrong address, under DHCP leases in the hAP was showing the hostname as being the IP address that it should have had based on a DHCP reservation and the Current DHCP Lease showing the assigned address and MAC. Unfortunately I did not screen capture this condition. The part that was consistent was that EVERY device that had the Do Not Propagate checkbox selected was in this incorrect state. I unselected the DNP box on one device and saved it in the hAP and then on the device (a router in the first case) I released and renewed the DHCP client and promptly got the correct address based on the DHCP reservation. I repeated the test on several other devices, with the same results. As soon as I unselected DNP and renewed the lease, the hAP assigned the correct address based on the DHCP reservation. Re-selecting the DNP checkbox and renewing the lease did not immediately result in an incorrect IP address being assigned.
Both of my hAPs are currently running 3.22.6.0
It's a couple hour later and on both hAPs, one of the devices that have a DHCP reservation with Do Not Poroagate checked has changed the hostname in the DHCP leases column to the IP address. When I did my earlier post, the host names were proper after unchecking DNP. So far, the IP has not changed. This time I took screen captures - before and after:
Would you please post this to our Issues List in GitHub? https://github.com/aredn/aredn/issues
Thanks,
Andre
Thanks!