Responding to your last response first, yes, my wording was kind of bad, but still true. It's getting an address from the wrong subnet, which is also the wrong pool of addresses.
The wireless nic is active on the device and has it's own IP reservation, I'll try disabling that when I test this again, but it's working perfectly right now with the DHCP relay and getting it's own IP address as well as the on board nic getting it's own address which is baffling why this isn't working. I'm not even sure how I'd look to see if I can follow along with the flow chart you referenced. I did apply the sanity-checks, but that didn't seem to fix anything as I'm still getting the same address from subnet 1 and not the reservation from subnet 2. This has turned into a bit of a beast, and my initial question has been more than answered, that the setting on the interfaces with UDP are intended for only relay situations, which is working as I'm expecting. I'd like to get away from the DHCP relay, but this is proving to be more than I thought it would be. Things are more or less working, so I think I'm fine for now and willing to let this go dormant. I really appreciate all of the pointers and advice. -Ubence On Sun, Aug 4, 2024 at 9:26 AM Sonic <[email protected]> wrote: > You might try adding this to your config: > > "sanity-checks": { > "lease-checks": "fix-del" > }, > -- > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. > > Kea-users mailing list > [email protected] > https://lists.isc.org/mailman/listinfo/kea-users >
-- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
