[RADIATOR] Proxy'ing Client-Identifier to "slave" RADIUS processes

[Robert Fisher]

You could build a custom vendor attribute by adding it to your 
dictionary on an
unused vendor id and then in the handler or client clause use an 
Add-To-Request to tack
on the value.   It would mean reconfiguring the slave or downstream 
instances so
those handlers matched on the new vendor attribute rather than 
Client-Identifier.

Alternatively, the NAS-Identifier would be preserved, but I imagine 
you're using
Client-Identifier to group similar clients together.

On 1/28/2013 11:42 AM, Johnson, Neil M wrote:
>
>
> I'm playing with running multiple instances of RADIATOR on the same 
> windows box to improve RADIATOR performance.
>
> I have a "Master" instance of RADIATOR that proxies incoming requests 
> from my  NAS boxes (wireless controllers) to one of four "slave" 
> instances using <AuthBy HASHBALANCE>.
>
> However,  I need to use different Handlers based on the incoming NAS 
> box.  Using a single instance of RADIATOR I would just use 
> "Identifier" keyword in the <Client> configuration clause and pick a 
> Handler using "Client-Identifier" selector in the <HANDLER> clause.
>
> Is there a way to pass the "Client-Identifier" to another RADIATOR 
> process ? Perhaps as an RADIUS Attribute ?
>
> Thanks.
> -Neil
>
> -- 
> Neil Johnson
> Network Engineer
> The University of Iowa
> Phone: 319 384-0938
> Fax: 319 335-2951
> Mobile: 319 540-2081
> E-Mail: neil-johnson at uiowa.edu
>
>
>
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.open.com.au/pipermail/radiator/attachments/20130128/dd94deba/attachment.html