Darren Ankney писал(а) 2023-07-15 06:15:
Hi Joe,
Random idea that may not work would be to try specifying "*" as the
interface. You can do that in the global interfaces-config (see first
example here:
https://kea.readthedocs.io/en/kea-2.4.0/arm/dhcp4-srv.html#interface-configuration),
for sure. I'm not sure that will be permitted in the pool statement,
however (probably not, but worth a try).
Thank you,
Darren Ankney
On Fri, Jul 14, 2023 at 7:04 AM Joe Botha <[email protected]> wrote:
Hi
Got a bit stuck with the client-class idea.
Even with classes forcing subnet selection based on the interface, Kea
will not respond unless an interface is defined within the subnet -
and we're back to the same problem, you can only define one interface
per subnet.
So we're using br0.30 as the test. br0.30 is defined at the global
level. If it's defined in the subnet as well, things work. If it's not
defined in the subnet level, things do not work.
Any advice to get around the one interface per subnet problem?
Maybe it could work if you insert option-82 indicating from what switch
port the client comes from.
Just a shot in the dark.
Kind regards,
Andrey
--
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
