On Sat, Aug 3, 2024 at 11:07 PM Ubence Quevedo <[email protected]> wrote: > I then did some digging into the lease file and logs and here's what I'm > seeing: > The /var/lib/kea-leases4.csv before the change and after. The only changes > are the subnet_id [from 2 [correct] to 1 [incorrect]] and the hostname: > address,hwaddr,client_id,valid_lifetime,expire,subnet_id,fqdn_fwd,fqdn_rev,hostname,state,user_context,pool_id > 192.168.11.118,c8:2a:14:45:53:24,01:c8:2a:14:45:53:24,28800,1722765662,2,1,1,mac-ubuntu-laptop-wired.totusmel.com,0,,0 > 192.168.10.227,c8:2a:14:45:53:24,01:c8:2a:14:45:53:24,28800,1722765662,1,1,1,ubuntu-system.totusmel.com,0,,0
Looks to me that the bug you should be shooting is "the device gets an address from the wrong subnet" instead of the device gets an address from the pool. Normally a device shuts down its wlan when its wired connection is active. Manually disable the subnet id1 interface (I don't know which interface is on which subnet) on the device and see if it gets the right IP address. Also quite weird that both interfaces would have the same mac address - have either one been overridden? Does the same thing happen for other devices that should be part of id2? Maybe the subnet selection flowchart can help: https://kea.readthedocs.io/en/kea-2.6.1/umls.html#dhcpv4-subnet-selection -- 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
