RE: (RADIATOR) Queries on proxy radius and config file auto refresh on Radiator Radius
Hi
Hugh
Thanks for the
reply, further queries on the two questions, using the client default resolves
the need to configure new RAS client in the Radiator but at my Radius Host i
still need to add the RAS client on it, I wasn't thinking if the Radiator can
strip off NAS-IP and replace it's IP on the NAS-IP attributesbefore
sending to the Radius Host so that at the Radius host it will always appears as
the Radiator IP instead of the RAS IP, this effectively helps me in controlling
the effort to configure new NAS-IP on the Radius Host. Is this feasible?
Thanks
RAS- Radiator
- Radius Host
# Remove any
NAS-IP-Address
StripFromRequest
NAS-IP-Address
# Append a Filter-ID
AddToRequest
Calling-Station-Id=1.1.1.1
Second
questions
Using kill - HUP ,
am I right to say, I can just do a kill -HUP Process ID on the radisud
process and it will take effect on the new updated config file? But I have this
problem when I do this, the Radiator is not able to write into the mySQL DB
anymore until a complete shutdown and restarton the apps and DB, then it
will returnto normal operation. Thanks
kill -HUP
Process ID of the process "perl radiusd -config_file config file
name"
Regards Brian Information Technology
-Original Message-From: Hugh Irvine
[mailto:[EMAIL PROTECTED]Sent: Saturday, July 19, 2003 8:46
AMTo: Brian CHNG Sing YongCc: '[EMAIL PROTECTED]'; CHEW
Yong SinSubject: Re: (RADIATOR) Queries on proxy radius and config
file auto refresh on Radiator Radius
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.
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
(RADIATOR) Queries on proxy radius and config file auto refresh on Radiator Radius
Title: 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 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
RE: (RADIATOR) Queries on proxy radius and config file auto refresh on Radiator Radius
Just kill -HUP the radiusd process when you've changed the configs Clients won't notice the difference - the re-read of the configs is very fast -Original Message- From: Brian CHNG Sing Yong [mailto:[EMAIL PROTECTED] Sent: 18 July 2003 16:23 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 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 === 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.
RE: (RADIATOR) Queries on proxy radius and config file auto refresh on Radiator Radius
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.
Re: (RADIATOR) Queries on proxy radius and config file auto refresh on Radiator Radius
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.
