You could use a PreHandlerHook in your Client clause like this->
<Client XXX.XXX.XXX.XXX>
Secret somesecret
PreHandlerHook sub
{${$_[0]}->change_attr('NAS-IP-Address','YYY.YYY.YYY.YYY');}
</Client>
This may cause unintended consequences with your downstream RADIUS servers
since all requests will now appear to be coming from the same NAS. I
personally would not reccomend it.
-----Original Message-----
From: Brian CHNG Sing Yong [mailto:[EMAIL PROTECTED]
Sent: Friday, July 18, 2003 11:23 AM
To: '[EMAIL PROTECTED]'
Cc: CHEW Yong Sin
Subject: (RADIATOR) Queries on proxy radius and config file auto refresh on
Radiator Radius
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
===
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.
