vendor-specific problem in 3.0.4 vs. 2.1.12

Rob McKennon rmckennon at
Thu Oct 8 15:44:54 CEST 2015


I'm trying to get super-micro's IPMI to work with freeradius.  Their 
latest docs say to use freeradius 2.1.12, and it does work.

Using this in the users file:

"radius_admin" Cleartext-Password := "123456"
                Vendor-Specific = "H=4, I=4"

I get the following results:

Found Auth-Type = PAP
# Executing group from file /usr/local/etc/raddb/sites-enabled/default
+- entering group PAP {...}
[pap] login attempt with password "123456"
[pap] Using clear text password "123456"
[pap] User authenticated successfully
++[pap] returns ok
# Executing section post-auth from file 
+- entering group post-auth {...}
++[exec] returns noop
Sending Access-Accept of id 0 to port 43540
     Vendor-Specific = 0x483d342c20493d34
Finished request 0.

But when I try using freeradius 3.0.4 with the same radius-admin user, I 
get this result:

(0) Sending Access-Accept packet to host port 38957, id=0, 
(0)     Vendor-Specific = UNKNOWN-TYPE
Sending Access-Accept Id 0 from 
<> to <>
     Vendor-Specific = UNKNOWN-TYPE
(0) ERROR: Failed sending reply: ERROR: Unknown attribute type 21
(0) Finished request

So, I'm not sure how version 3 differs from version 2.1.12 in handling 
of the Vendor-specific attributes, but is there a way to make this work 
in version 3 / something I need to tweak?


More information about the Freeradius-Users mailing list