Send kea-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."
Today's Topics:
1. Re: boot-unknown-clients equivalent? (Philip Prindeville)
----------------------------------------------------------------------
Message: 1
Date: Tue, 16 May 2023 12:23:30 -0600
From: Philip Prindeville <[email protected]>
To: Peter Davies <[email protected]>
Cc: [email protected]
Subject: Re: [kea-dev] boot-unknown-clients equivalent?
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=us-ascii
> On Apr 30, 2023, at 4:48 AM, Peter Davies <[email protected]> wrote:
>
> Hi Philip,
>
> If you only employ host reservations, then the built-in "KNOW" class may be
> use to restrict clients.
>
> For example:
>
> "client-classes": [{
> "name": "DROP",
> "test": "not member('KNOWN')"} ],
>
> ...
>
> I advise caution, as this will drop all packet that are not associated with a
> host reservation.
>
> /Peter
This goes where? Inside the subnet definition?
Also, isn't the point of "boot-unknown-client false;" exactly that -- to drop
requests that don't match a static host reservation if that's how your managing
your subnets?
Thanks
------------------------------
Subject: Digest Footer
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
------------------------------
End of kea-dev Digest, Vol 85, Issue 2
**************************************
