Adding Vendor Specific Attribute to the Access-Accept

[normal ozone]

Thanks for the reply.

Correct me if I'm wrong but the NAS is the one sending authentication requests 
to the radius server?
In my setup's case the one sending radius requests is a PC. I'm using the 
TinyRadius library.
So technically I can use any of the radius attributes. I plan to use a company's 
vendor specific
attribute. But will this have other repercussions? Legally, technically?

Regards,




________________________________
From: Alan Buxey <A.L.M.Buxey at lboro.ac.uk>
To: FreeRadius users mailing list <freeradius-users at lists.freeradius.org>
Sent: Mon, May 2, 2011 11:03:00 PM
Subject: Re: Adding Vendor Specific Attribute to the Access-Accept

Hi,

>    I found the reason why the attributes I added where not
>    included in the reply list. Those attributes are used by the servers
>    internally (Range:  1000-1199)
>    They do not go to the reply attributes list.
> 
>    When I tried the attributes from other vendors like 3Com it worked.
>    The reply attributes were included in the Access-Accept message.

you need to use attributes that your NAS understands and will use - check
your NAS documentation and the dictionary files.

alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20110503/15ce2e1b/attachment.html>