Klaus,
My suggestion only works if there is a pattern to the way the relay
IPs are chosen. Specifically, if they are grouped together such that
they COULD be subnetted, but are not on the switch side. You would be
pretending (on the Kea side) that they are. Then you could add these
subnets as
Klaus Steden wrote:
> … so it’s been an uphill battle just to push for basic changes like "let's
> use one DHCP server for multiple subnets instead of standing up a separate
> local DHCP server on each subnet because L3 is not actually that complicated".
I guess you can be grateful for the
Hello Simon,
Thank you for demystifying this.
FWIW we are already using MySQL to store lease and reservation data, and we
built an API to manage leases and reservations years ago that is also
integrated with our config management service, which we use to update the
Kea config (e.g.,
