Send kea-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."
Today's Topics:
1. Re: Quoting integer values (Francis Dupont)
2. Re: Quoting integer values (Philip Prindeville)
3. Re: Quoting integer values (Francis Dupont)
----------------------------------------------------------------------
Message: 1
Date: Fri, 16 Jan 2026 12:45:50 +0000
From: Francis Dupont <[email protected]>
To: Philip Prindeville <[email protected]>
Cc: [email protected]
Subject: Re: [kea-dev] Quoting integer values
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Philip Prindeville writes:
> I'm looking at this table:
>
> https://kea.readthedocs.io/en/stable/arm/dhcp4-srv.html#id6
>
> Where it says that "dhcp-renewal-time" is a uint32 but I need to encode it as
> a string in the config file:
>
> Syntax check failed with: /etc/kea/kea-dhcp4.conf:191.25-28: syntax error, un
> expected integer, expecting constant string
>
> Or I get the above message:
>
> 189 {
> 190 "name": "dhcp-renewal-time",
> 191 "data": 1800,
> 192 "always-send": true
> 193 }
>
> Why?
=> data value is a string which when csv-format is true (the default)
is interpreted according to the option definition so you must put
"data": "1800",
and the option will take the 1800 value.
> Other things like "valid-lifetime" don't require quotes.
=> "valid-lifetime" value is an integer.
Just look at the grammar of the config file (or the bison file but
the grammar is the doc is supposed to be easier to read...).
Thanks
Francis Dupont <[email protected]>
------------------------------
Message: 2
Date: Fri, 16 Jan 2026 10:18:26 -0700
From: Philip Prindeville <[email protected]>
To: Francis Dupont <[email protected]>
Cc: [email protected]
Subject: Re: [kea-dev] Quoting integer values
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=utf-8
> On Jan 16, 2026, at 5:45?AM, Francis Dupont <[email protected]> wrote:
>
> Philip Prindeville writes:
>> I'm looking at this table:
>>
>> https://kea.readthedocs.io/en/stable/arm/dhcp4-srv.html#id6
>>
>> Where it says that "dhcp-renewal-time" is a uint32 but I need to encode it as
>> a string in the config file:
>>
>> Syntax check failed with: /etc/kea/kea-dhcp4.conf:191.25-28: syntax error, un
>> expected integer, expecting constant string
>>
>> Or I get the above message:
>>
>> 189 {
>> 190 "name": "dhcp-renewal-time",
>> 191 "data": 1800,
>> 192 "always-send": true
>> 193 }
>>
>> Why?
>
> => data value is a string which when csv-format is true (the default)
> is interpreted according to the option definition so you must put
> "data": "1800",
> and the option will take the 1800 value.
I tried adding
"csv-format":false
above but it still needs a string and not an integer.
>
>> Other things like "valid-lifetime" don't require quotes.
>
> => "valid-lifetime" value is an integer.
>
> Just look at the grammar of the config file (or the bison file but
> the grammar is the doc is supposed to be easier to read...).
>
> Thanks
>
> Francis Dupont <[email protected]>
------------------------------
Message: 3
Date: Fri, 16 Jan 2026 21:44:04 +0000
From: Francis Dupont <[email protected]>
To: Philip Prindeville <[email protected]>
Cc: Francis Dupont <[email protected]>, [email protected]
Subject: Re: [kea-dev] Quoting integer values
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Philip Prindeville writes:
> > => data value is a string which when csv-format is true (the default)
> > is interpreted according to the option definition so you must put
> > "data": "1800",
> > and the option will take the 1800 value.
=> perhaps you need the other case: data value is a string which when
csv-format is false must contains the value in hexadecimal or
(single) quoted litteral (e.g. "'foo'" or "666f6f").
The grammar is (in EBNF):
option_data_data ::= "data" ":" STRING
Thanks
Francis Dupont <[email protected]>
------------------------------
Subject: Digest Footer
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
------------------------------
End of kea-dev Digest, Vol 100, Issue 3
***************************************
