[Kea-users] CIDR or range notation in relay lists when using shared-networks?

[Darren Ankney]

Hello Klaus,

In addition to what Peter said, another option would be to use shared
networks and add the subnet for relays along with the subnet of
addresses that you wish to allocate to the clients to a shared
network.  See: https://kea.readthedocs.io/en/kea-2.2.0/arm/dhcp4-srv.html#shared-networks-in-dhcpv4

Example:

{
"Dhcp4": {
    "shared-networks": [
        {
           "subnet4": [
                {
                    // relays
                    "subnet": "10.1.0.0/21"
                },
                {
                    // client subnet
                    "subnet": "192.0.2.0/24",
                    "pools": [ { "pool":  "192.0.2.100 - 192.0.2.199" } ]
                }
            ]
        }
     ]
  }
}


On Tue, Feb 21, 2023 at 9:45 PM Klaus Steden <klausfiend at gmail.com> wrote:
>
>
> Hi there,
>
> In some of our environments, we deal with DHCP relays, and their addresses seem to proliferate faster than we can update our configs, which leads to delays with DHCP service.
>
> However, they have reserved an entire /21 for relay IPs, and ideally, I would like to be able to add that entire network as a relay instead of what I'm currently doing, which is adding individual IPs when I notice them reported in the log.
>
> Is this even possible? The examples in the Kea documentation only mention single addresses, but for big networks with lots of relays like ours, it would be very helpful to be able to just add an entire range of IPs and have Kea figure it out automatically.
>
> thanks,
> Klaus
> --
> 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
> Kea-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users