You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A little confused by the example configuration. It appears by default that netbox-kea-dhcp will take the first address and last address and build the DHCP pool in Kea. The configuration example shows this:
Default pool<->IP range map: no map
#[pool_iprange_map]
Is this a way to customize or preferentially, turn off the pool? What directive is this section looking for?
The text was updated successfully, but these errors were encountered:
Hi,
You’r right about the first and last addresses of the IP range translated to the first and last addresses of the Kea pool. This mapping is hard coded so it isn’t customizable in config file. To turn off the pool, you can use the range filter:
[iprange_filter]status = "dhcp"
… and never assign the "dhcp" value to range status (a value which, by the way, does not exist in netbox 3.4). No pool will be created. And if a pool linked the the IP range already exist in Kea, it will be removed.
The section [pool_iprange_map] may accept any parameters other than start and end IP addresses. You may want to create custom attributes in netbox and use them to assign a DHCP options (like options 66 and 67 for PXE boot) to the pool.
A little confused by the example configuration. It appears by default that netbox-kea-dhcp will take the first address and last address and build the DHCP pool in Kea. The configuration example shows this:
Default pool<->IP range map: no map
#[pool_iprange_map]
Is this a way to customize or preferentially, turn off the pool? What directive is this section looking for?
The text was updated successfully, but these errors were encountered: