I hope you have understand my problem right, but i will try to re explain it. i want to add the vp list in a VSA like following. (the way that NTRadping utility sends the vps) VSA ->vp ->vp ->vp This problem is my bottle line for me and i have to do it, because the client's application knows the attributes that way. please guide me where and what are the code changes that i have to make, and what structure i have to follow. special thanks. Regards FQ
Message: 6 Date: Thu, 13 Sep 2007 07:28:45 +0200 From: Alan DeKok <aland@deployingradius.com> Subject: Re: Reply VSA Attributes in a list To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Message-ID: <46E8CA8D.5020606@deployingradius.com> Content-Type: text/plain; charset=ISO-8859-1
Faqeer ALI wrote:
In the response packet i want to add the VPS such that the VSA of one vendor attaches in a specific vendor list, ie specify the vendor once and then the list of attributes in it.
You mean inside of the RADIUS packet?
By pairadd(&request->reply->vps,vp) the vps are added one after the another, but i want it such that there would be the name of the specific vendor once and list of attributes to follow behind it..
The VALUE_PAIRs don't work that way.
For a number of reasons, FreeRADIUS doesn't pack multiple VSA's into one Vendor-Specific attribute. There are interoperability issues, and it would also require code changes.
Alan DeKok.
_________________________________________________________________ Gear up for Halo® 3 with free downloads and an exclusive offer. http://gethalo3gear.com?ocid=SeptemberWLHalo3_MSNHMTxt_1
Faqeer ALI wrote:
i want to add the vp list in a VSA like following. (the way that NTRadping utility sends the vps) VSA ->vp ->vp ->vp
If you want them in that format, then add them in that format. The server doesn't re-order VSAs. And you *are* aware that the VALUE_PAIR structure and lists are independent from the attributes in the packet, right? Are you sure you understood my response?
This problem is my bottle line for me and i have to do it, because the client's application knows the attributes that way.
The client application is broken. Fix it. http://freeradius.org/rfc/rfc2865.html Section 5: ... A RADIUS server or client MUST NOT have any dependencies on the order of attributes of different types. ...
please guide me where and what are the code changes that i have to make, and what structure i have to follow.
Fix the client program. It is NOT following the RADIUS specification. FreeRADIUS is fine. If you *do* want to fix FreeRADIUS, you have all of the code in front of you. There's even comments explaining what the code does. If you have *specific* questions about FreeRADIUS, then ask them. Otherwise, you're asking us to (essentially) implement the solution for you. Alan DeKok.
participants (2)
-
Alan DeKok -
Faqeer ALI