(RADIATOR) Clients in handlers?

CONDOR condor at inreach.com
Fri Sep 7 23:39:51 CDT 2001


Yes I understand that stuff pretty well now.

I guess if I diddle with the BogoMips and fallback times I can cause it to
 not request to alternate servers as handily.

On Friday, September 07, 2001 17:56, Hugh Irvine [SMTP:hugh at open.com.au] 
wrote:
> Hello Todd -
>
> Let me try to clarify what happens with radius clients and servers.
>
> NAS clients or NAS groups are radius clients, and send radius requests to a
> radius server. Radiator is a radius server and can be configured to accept
> radius requests from one of more radius clients.
>
> Further, Radiator can be configured to proxy radius requests to other
> radius servers, in which case, Radiator acts as a radius client. The AuthBy
> RADIUS clause in Radiator is the radius client code which acts as a radius
> client when sending requests to a proxy server.
>
> In addition, there are several load balancing proxy clauses such as AuthBy
> LOADBALANCE, AuthBy VOLUMEBALANCE and AuthBy ROUNDROBIN, which can be
> configured to send requests to multiple proxy servers. Note that Radiator
> is still acting as a radius client in this scenario.
>
> In other words, there are radius requests from NAS clients and NAS groups
> coming in to Radiator acting as a server, and there are radius requests
> sent by Radiator when acting as a proxy client and sending to a proxy
> server.
>
> hth
>
> Hugh

-------------------------------------------------------
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.


More information about the radiator mailing list