From e7ec23bae9f453d577de429dbc37917afda60f0a Mon Sep 17 00:00:00 2001 From: Francis Dupont Date: Sat, 13 Sep 2025 00:10:48 +0200 Subject: [PATCH] [#3860] Addressed comment --- doc/sphinx/arm/ext-radius.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/sphinx/arm/ext-radius.rst b/doc/sphinx/arm/ext-radius.rst index 6427d1a057..4bf8178def 100644 --- a/doc/sphinx/arm/ext-radius.rst +++ b/doc/sphinx/arm/ext-radius.rst @@ -227,7 +227,7 @@ At the service level, three sections can be configured: It specifies an evaluation expression on the DHCP query packet. - ``vendor`` - since Kea 3.1.2 is the vendor id of the attribute. - It allways contents a string with the vendor name or an integer litteral. + It always contains a string with the vendor name or an integer literal. Attributes are supported only for the access service. @@ -529,7 +529,7 @@ RADIUS dictionary. There are differences: * - Support for Attribute Data Types - - string, ipaddr, ipv4prefix, integer, integer64, date, ifid, ipv6addr, ipv6prefix, tlv, abinary, byte, ether, short, signed, octets + - string, ipaddr, ipv4prefix, integer, integer64, date, ifid, ipv6addr, ipv6prefix, tlv, binary, byte, ether, short, signed, octets - string (can simulate any other unsupported data type too), ipaddr, integer, date (interpreted as integer), ipv6addr, ipv6prefix -- 2.47.3