We migrated from dhcpd to kea 2.0 almost 2 months ago. Everything has been going well with the exception of a seemingly perplexing behavior difference between the two DHCP implementations.
We have a lot of embedded devices of varying age all dhcping. All of these devices had been working nominally when using dhcpd. However we are noticing that when a device has a /technically/ non-compliant fqdn in the option 81 field, kea will silently drop the DISCOVER packet. Some of the devices we’ve been able to upgrade or fix the configuration, but many devices can’t be fixed and would need to be replaced. I’m curious if anyone else has noticed this behavior and if so has anyone figured out a work around? -- Munroe Sollog (He/Him/His) Network Architect [email protected]
-- 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
