Hi Wilhelm,
A question: Is option 13 a sub option of 9 which is a sub option of
option 82? Or, is option 13 a sub option of option 82 along with
option 9?
Also, note that you can access option 82 sub options with:
relay4[9].hex == 'some string' which accesses option[82].option[9]
if both 9 and 13 are sub options of 82, then something like this will
probably work:
"client-classes": [
{
"name": "test",
"test": "relay4[9].hex == 'some string' and relay4[13].hex ==
'some other string'"
}
],
Thank you,
Darren Ankney
On Tue, Sep 23, 2025 at 9:57 AM Wilhelm Wijkander <[email protected]> wrote:
>
> Hello,
> I was wondering if there is any good way of accessing the
> sub-option/TLVs inside of option 82 sub-options? In my case I'd like
> to classify clients based on:
>
> option[82].option[9].option[13].hex
>
> Where option 13 is a vendor-specific suboption inside the
> vendor-specific-information suboption of option 82. But Keas parser
> does not accept this.
>
> As a workaround I could of course take a substring from
> option[82].option[9].hex with an offset, but this feels quite fragile
> as it relies on the ordering of the vendor specific sub-options being
> the exact same all the time.
>
> Thankful for any help,
> Wilhelm
> --
> 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]
--
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]
