Hello,
i'm trying to set a special value for "valid-lifetime" with a globally
defined client-class:
"valid-lifetime" : 3333,
...
"client-classes" : [
{
"name" : "InfiniteLease",
"valid-lifetime": 4294967295,
"option-data" : [
{
"code" : 6,
"data" : "1.2.3.4",
"name" : "domain-name-servers"
}
]
}
later on in the configuration i have
"shared-networks" : [
{
"name" : "DHCP-Test",
"subnet4" : [
{
"id" : 1,
"option-data" : [
{
"data" : "9.8.7.6",
"name" : "domain-name-servers"
},
...
],
"reservations" : [
{
"client-classes" : [
"InfiniteLease",
],
"hostname" : "testpc-kea",
"hw-address" : "00:17:C3:C2:73:E3",
"ip-address" : "5.6.7.8",
"option-data" : [
{
"data" : "testpc-kea",
"name" : "host-name"
},
{
"data" : "example.org",
"name" : "domain-name"
}
] #option-data
} #testpc-kea
] #reservations
} #subnet4
} #DHCP-Test
] #shared-networks
In this scenario the client testpc-kea doesn't get the expected
valid-lifetime of 4294967295, but instead the default of 3333. But it
_does_ get domain-name-servers="1.2.3.4", so i can tell that it is
associated with the client-class=InfiniteLease".
In a second test i removed the shared-networks[] from the configuration.
When i have only the subnet4-declaration the clients gets
"valid-lifetime"= 4294967295 as intended (and also
domain-name-servers="1.2.3.4"). The only difference is the removal of
shared-networks.
This seems a bit confusing to me. Is this a bug in kea or is the
shared-networks-declaration changing the scope of valid-lifetime in an
(for me) unexpected way?
Any help or explanation is appreciated.
Thanks,
Kurt
--
Kurt Kesper
Abteilung Kommunikation
Hochschulrechenzentrum (HRZ)
Philipps-Universität Marburg
Hans-Meerwein-Straße 6
35032 Marburg
https://www.uni-marburg.de/de/hrz
--
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.
[email protected]
