[RADIATOR] Remote RADIUS servers (proxying)

[rohan.henry @cwjamaica.com]

Michael,

I would prefer not to completely disable it since other Handlers are using
it. I only want it disabled for a particular Handler.

Rohan


On Fri, Nov 29, 2013 at 5:19 PM, Michael <ringo at vianet.ca> wrote:

>
> 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>
> RetryTimeout 2
> </Host>
>   <Host server2.domain.com>
>   Secret secret2
> </Host>
> </AuthBy>
>
>
>
> _______________________________________________
> radiator mailing listradiator at open.com.auhttp://www.open.com.au/mailman/listinfo/radiator
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.open.com.au/pipermail/radiator/attachments/20131129/fd23e673/attachment.html