(RADIATOR) Queries on proxy radius and config file auto refresh on Radiator Radius

[Hugh Irvine]

Hello Brian -

For your first question, you can use the AuthBy SQLRADIUS clause for 
your radius proxy targets, and you can use a Client DEFAULT to match 
any number of client devices.

<Client DEFAULT>
	.....
</Client>

See section 6.45 in the Radiator 3.6 reference manual ("doc/ref.html").

For your second question, you can send the radiusd process a HUP signal 
to perform a warm restart.

See section 7 in the manual.

regards

Hugh


On Saturday, Jul 19, 2003, at 01:22 Australia/Melbourne, Brian CHNG 
Sing Yong wrote:

> Hi
>
> I've just deployed Radiator Radius in my workplace but am facing some 
> problems with having to make changes so often and creating many 
> downtimes on my servers. Would appreciate if you can help me with the 
> following questions. Thanks
>
> First Question
>
> I'm doing proxy radius to multiple host and I want to minimize having 
> to configure the Radius Host each time a new RAS is deployed, by 
> default the Radiator will forward all Radius Attributes to the Radius 
> host and on the Radius host I would need to configure the NAS-IP so 
> that it will accept the authentication/accounting packet from the RAS 
> Client. I'm looking at how to minimize changes made on the Radius Host 
> as I would need to restart the Radius Host whenever a change is made. 
> Can I configure the Radiator in such a way that it will strip off the 
> NAS-IP and replace it with its own IP as the NAS-IP so that the Radius 
> host will only see one NAS-IP or RAS Client IP? In this way I'll never 
> need to add RAS Client on the Radius host. Or is there any other 
> better way to tackle this? Thanks
>
> eg
>
> RAS1 à Radiator1 à Radius1
>
> RAS2 à Radiator1 à Radius2
>
> RAS3 à Radiator1 à Radius3
>
> Second Question
>
> Can I configure the Radiator to re-read the config file or clear the 
> cache at regular interval so that any changes made on the config file 
> can be refreshed and take effect without having to restart the 
> processes which also means downtime needed, I'm trying to figure out 
> how the Radiator can be configured to minimize downtime. Thanks
>
> Regards
>
> Brian
>
>
> This email is confidential and privileged.  If you are not the 
> intended recipient, you must not view, disseminate, use or copy this 
> email. Kindly notify the sender immediately, and delete this email 
> from your system. Thank you.
>
> Please visit our website at www.starhub.com
>
>

NB: have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 4919 bytes
Desc: not available
URL: <http://www.open.com.au/pipermail/radiator/attachments/20030719/b679f5d3/attachment.bin>