(RADIATOR) Radiator behaviour as Proxy radius server

[Hugh Irvine]

Hello Abdul Rehman -

When you configure Radiator to operate as a radius proxy, it will send all 
radius requests to the radius target including authentication and accounting. 
If you wish to record the accounting records locally as well, that is very 
easy to accomplish. Here is an example:

# define AuthBy clauses

<AuthBy RADIUS>
	Identifier ProxyToTarget
	.....
</AuthBy>

<AuthBy SQL>
	Identifier LocalAccounting
	......
	AuthSelect
	AccountingTable ACCOUNTING
	AcctColumnDef .....
	......
</AuthBy>

# define Realms or Handlers

<Realm ....>
	AuthByPolicy ContinueAlways
	AuthBy LocalAccounting
	AuthBy ProxyToTarget
	......
</Realm>

regards

Hugh


On Friday 26 October 2001 04:22, Abdul Rehman Saeed wrote:
> Hi,
>
> I have a question regarding Radiator implementation as a proxy radius
> server and how it handel accounting requests.
>
> If we have Target Radiator Server(T) and Proxy Radiator Server (P),
> Where account request will be recorded?  at P or at T
> Is there any way that we force Radiator to record account request at Target
> server (T) or both.
>
>
>
>
>
> Thanks.
>
>
> Abdul Rehman Saeed

----------------------------------------
Content-Type: text/html; charset="iso-8859-1"; name="Attachment: 1"
Content-Transfer-Encoding: quoted-printable
Content-Description: 
----------------------------------------

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
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.