Must use 'Attr-26 = ...' instead of 'Vendor-Specific = ...' even when setting explicitly Attr-26 (or vendor data type)

[Francesco Di Nucci]

Thank you,

tried and reply:Attr-26 := 0x483D342C20493D34 /without quotes/ still 
returns Cannot parse RHS hex as the data type of the attribute 
Vendor-Specific.

Same for reply:Attr-26 := 0x1A1200002A7C483D342C20493D34 without 
quotes... Cannot parse RHS hex as the data type of the attribute 
Vendor-Specific

What else could be wrong?

Best regards

Francesco

-- 
Francesco Di Nucci
System Administrator
Compute & Networking Service, INFN Naples

Email:francesco.dinucci at na.infn.it

On 24/04/26 14:01, Alan DeKok via Freeradius-Users wrote:
> On Apr 24, 2026, at 6:06 AM, Francesco Di Nucci<francesco.dinucci at na.infn.it> wrote:
>> I am using FreeRADIUS 3.0.27 on EL9, and I'm trying to set a Vendor Attribute in replies.
>>
>> For context, I am trying to authenticate SuperMicro BMCs with LDAP (see threadhttps://lists.freeradius.org/pipermail/freeradius-users/2018-March/091085.html)
>>
>> So in my enabled site I edited the post-auth section
>>
>> post-auth {
>>      update {
>>          reply:Attr-26 := "0x483D342C20493D34"
>    That's a double quoted string.  The "0x" text is part of the string.
>
>> This results in "Cannot parse RHS hex as the data type of the attribute Vendor-Specific"
>    Exactly it can't parse it as hex, because it's not hex.  It's a double quoted string.
>
>
>
>> As it's missing Vendor ID, I tried to add it. Super Micro PEN on IANA is 10876, so full vendor attribute should be 1A1200002A7C483D342C20493D34 if I am correct:
>>
>> post-auth {
>>      update {
>>          reply:Attr-26 := "1A1200002A7C483D342C20493D34"
>    Drop the quotes.  Use:
>
> 	reply:Attr-26 := 0x1A1200002A7C483D342C20493D34
>
>    The server has tests for this, so it should work.
>
>    Alan DeKok.
>
>
> -
> List info/subscribe/unsubscribe? Seehttp://www.freeradius.org/list/users.html