Problems decoding a vendor-specified attribute on the client side
1.41421 at gmail.com
Thu Dec 27 06:09:57 CET 2012
More comments below.
On Wed, Dec 26, 2012 at 8:49 PM, Alan DeKok <aland at deployingradius.com> wrote:
> JCA wrote:
>> I added the VENDOR definition that I mentioned above to both client
>> and server already.
> And the attribute? Note also that the dictionary file format is NOT
> the same for the client and server code.
OK, that was the problem. I was using the same format for both. I
couldn't find any information about the format for the dictionary file
in the FreeRADIUS 1.1.6 client sources, but a Google search quickly
returned the answer. Thanks for your feedback.
>> I included the code because I can't understand how it could ever
>> work. How can the comparison between attr->value and attribute, as I
>> described, ever succeed? The value of attribute as received from
>> rc_avpair_gen() contains both the vendor ID and the attribute
>> identifier, whereas the value of attr->value only contains the
>> attribute identifier. This comparison can never succeed.
> My reading of the code shows that the dictionary attribute contains
> the vendor ID... just like the data taken from the packet. See dict.c.
> Alan DeKok.
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
More information about the Freeradius-Devel