So..
This sets timers to the whole subnet. But when trying to apply only in a
pool then "spurious parameter" error occurs.
Thanks anyway.
Jeronimo
Em sex., 27 de ago. de 2021 às 12:51, perl-list
escreveu:
> Yes. You can do it just like this in the subnet section (this is for
> DHCPv6 but i im
Yes. You can do it just like this in the subnet section (this is for DHCPv6
but i imagine v4 is similar):
"subnet6": [
{
"valid-lifetime": 600,
"preferred-lifetime": 540,
"subnet": "2001:0
Hi,
Is there a way to configure a specific "valid-lifetimer" value for a pool
inside a subnet?
Regards,
Jeronimo
___
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more inform
YES :-)
That's the work around. Thanks !!
On 27/08/2021 15:42, Andrei Pavel wrote:
ip link add x type bridge
___
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more info
I have not used kea, but if it has an "include" directive similar to dhcpd,
then I would recommend using that in one of several ways:
(this is what I do at U of Michigan)
--- interface in top level, main config in separate file:
"interfaces-config": {
"interfaces": [
"x"
],
"dhcp-socket-type":
Checking every configuration bits for production is definitively an
excellent thing. But one could have an option to skip validating some
part(s) of them.
On 27/08/2021 15:38, perl-list wrote:
I understand, but you don't have to put the configuration file in its final
home, you could drop it
Mocking the interface on the test system as a root user will work:
ip link add x type bridge
On 27/08/2021 16:38, perl-list wrote:
I understand, but you don't have to put the configuration file in its final
home, you could drop it in /tmp/ or equivalent and run kea-dhcp4 -t
/tmp/kea-dhcp4
I understand, but you don't have to put the configuration file in its final
home, you could drop it in /tmp/ or equivalent and run kea-dhcp4 -t
/tmp/kea-dhcp4.conf and then copy it into place if it passes the test.
I doubt that ISC is going to be keen to not check certain bits of the
configurat
We want to be able to validate the configuration file without
touching/accessing the production servers, for example for
developing/testing/validating changes in the software that generates the
configuration file.
On 27/08/2021 15:12, perl-list wrote:
Is it not possible to, instead, check the
Is it not possible to, instead, check the conf file on host2 where it will live?
- Original Message -
> From: "Veronique Lefebure"
> To: "kea-users"
> Sent: Friday, August 27, 2021 5:39:15 AM
> Subject: [Kea-users] kea-dhcp4 -t file: check the configuration file syntax
> and exit but fa
Hi,
Before deploying a new kea configuration file on our DHCP server, we
want to validate it.
The configuration file "kea-dhcp4.conf" is generated on host1 where we
want to validate it by running
kea-dhcp4 -t kea-dhcp4.conf
And once validation has passed, we plan to deploy "kea-dhcp4.c
11 matches
Mail list logo