[RADIATOR] Remote RADIUS servers (proxying)

[Michael]

doesn't a handler process it by default?

I think you have to disable it.  I do it like this:
<SessionDatabase NULL>
         Identifier NULL
</SessionDatabase NULL>

then in your handler, specify :
SessionDatabase NULL

Note: NULL is not a command or configuration, but an Identifier.




On 29/11/13 04:50 PM, rohan.henry @cwjamaica.com wrote:
>
> Hello,
>
> I have configured a Handler clause to proxy Radius requests to a 
> remote server. Why is Radiator processing one of my sessions database 
> configuration even though I have not specified one under the Handler. 
> The SessionDatabase entry is commented out.
>
> See sample config below.
>
> <Handler NAS-Identifier="NAS1">
> # AddToRequest SERVICESTATUS = ACTIVE
> # SessionDatabase SQLSDB
> # MaxSessions 1
> RejectHasReason
>
> #AuthByPolicy ContinueAlways
> # AuthBy SQLStart
> # AuthBy SQLStop
> # AuthBy xDSL
>
> # Proxy requests to production radius server
> <AuthBy RADIUS>
>   Secret secret1
>   <Host server1.domain.com <http://server1.domain.com>>
> RetryTimeout 2
> </Host>
>   <Host server2.domain.com <http://server2.domain.com>>
>   Secret secret2
> </Host>
> </AuthBy>
>
>
>
> _______________________________________________
> 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/20131129/a5e282d4/attachment.html