Hi,
On 18 Dec 2025, at 14:07, lejeczek via Kea-users wrote:
> I've been trying - thinking is the easiest to read - this syntax:
> ```
> ...
> "client-classes": [
> {
> "name": "VMWARE",
> "test": "(pkt4.mac == 0x02981b6d3612 or pkt4.mac ==
> 0x0202bf56c0a0 or pkt4.mac == 029df779a717 or pkt4.mac == 02f6e218dd40 or
> pkt4.mac == 02a632946d96 or pkt4.mac == 027aeb9b8715 or pkt4.mac ==
> 029521b6cb87 or pkt4.mac == 02804c4e9f14)",
> "option-data": [
> ...
> ```
> but KEA fails with:
>
> kea-dhcp4[1919448]: 2025-12-18 14:03:14.719 ERROR
> [kea-dhcp4.dhcp4/1919448.140155453429888] DHCP4_PARSER_FAIL failed to create
> or run parser for configuration element client-classes: expression:
> [(pkt4.mac == 0x02981b6d3612 or pkt4.mac == 0x0202bf56c0a0 or pkt4.mac ==
> 029df779a717 or pkt4.mac == 02f6e218dd40 or pkt4.mac == 02a632946d96 or
> pkt4.mac == 027aeb9b8715 or pkt4.mac == 029521b6cb87 or pkt4.mac ==
> 02804c4e9f14)] error: <string>:1.77: Invalid character: d at
> (/etc/kea/kea-dhcp4.conf:21:21)
>
>
> is it because of KEA version which in my case is 2.6.4 ?
no, it is probably because only the first two hardware addresses are proper
Hex-Addresses (0x0202bf56c0a0), and the remaining ones are not hexadecimal
(missing the leading 0x = 027aeb9b8715 should be 0x027aeb9b8715)
Greetings
Carsten
--
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]
