It may well be compliant, but that doesn't change the reality that I
have devices, which cannot be updated, that are unable to accept the
"compliant" response. This requires that some other DHCP server be on
the net at the same time (see: dnsmasq) or that all non-"compliant"
legacy and new hardware be statically assigned. Please, allow the
administrator to override or suppress that "compliant" or unwanted
response(s).
On 2022-06-07 2:30 pm, Kevin P. Fleming wrote:
On Tue, Jun 7, 2022 at 3:15 PM Erik Edwards via Kea-users
<[email protected]> wrote:
I second this. I have several network switches that choke on the
returned option.
This appears to be RFC-compliant behavior on Kea's part, based on
section 3 of RFC 6842: https://www.rfc-editor.org/rfc/rfc6842.
--
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
