---------- Forwarded Message ----------
Subject: BOUNCE [EMAIL PROTECTED]: Non-member submission from [CONDOR
<[EMAIL PROTECTED]>]
Date: Fri, 7 Sep 2001 21:52:21 -0500
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
>From [EMAIL PROTECTED] Fri Sep 7 21:52:21 2001
Received: from mail.inreach.com ([EMAIL PROTECTED] [209.142.2.35])
by server1.open.com.au (8.11.0/8.11.0) with ESMTP id f882qL302953
for <[EMAIL PROTECTED]>; Fri, 7 Sep 2001 21:52:21 -0500
Received: from condor (209-142-19-144.stk.inreach.net [209.142.19.144])
by mail.inreach.com (8.11.3/8.11.2) with SMTP id f884dns31751
for <[EMAIL PROTECTED]>; Fri, 7 Sep 2001 21:39:49 -0700
Received: by localhost with Microsoft MAPI; Fri, 7 Sep 2001 21:39:52 -0700
Message-ID: <[EMAIL PROTECTED]>
From: CONDOR <[EMAIL PROTECTED]>
Reply-To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Subject: RE: (RADIATOR) Clients in handlers?
Date: Fri, 7 Sep 2001 21:39:51 -0700
Organization: Condor Worldwide Data Systems
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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:[EMAIL PROTECTED]]
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 [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
