[RADIATOR] Multiple radiator instances on single server?

Hugh Irvine hugh at open.com.au
Mon Oct 11 17:16:19 CDT 2010


Hi Dave, Hi Greg -

You can also use "include …" files to simplify configuration file management.

regards

Hugh


On 12 Oct 2010, at 05:37, Dave Kitabjian wrote:

> fyi,
> 
> You can also run separate instances with all pointing to a common config
> file, if that's simpler. That works if you can "override" everything
> instance-specific by using different command line arguments.
> 
> A single config file can be easier to manage if they will otherwise
> duplicate a lot of the same configuration details, hooks, etc.
> 
> Dave
> 
> -----Original Message-----
> From: radiator-bounces at open.com.au [mailto:radiator-bounces at open.com.au]
> On Behalf Of Gregory Fuller
> Sent: Thursday, October 07, 2010 10:42 AM
> To: radiator at open.com.au
> Subject: [RADIATOR] Multiple radiator instances on single server?
> 
> I'd like to go through and separate out my authentication, accounting,
> and tacacsplus radiator configurations each into its own separate
> radiator instance on the same server.  One radiator process would run
> just the radius authentication, one process for radius accounting, and
> one process for all tacacsplus auth/accounting.  I'm running Radiator
> 4.5 under CentOS 5.4.
> 
> I know I can start another process from the commad line and pass my
> different config files into it without any problems.  Within the
> config files I have separated out the different parts of the config
> for each operation and made sure only the port #'s I want to listen on
> are listed in the configs.
> 
> How are most places handling the running of multiple radiator
> instances on the same server using the standard RedHat/CentOS
> "services" functionalty?  Did you copy and rename /etc/init.d/radiator
> for each one of the services and modify each service script to load
> different config files on startup?
> 
> Just trying to figure out the best way to manage this.  I'd like to be
> able to do something like the following:
> 
> For radius authentication:	service radiator start
> For radius accounting:	service radiator-acct start
> For tacacs auth/accounting:	service radiator-tacacs start
> 
> Any sample RedHat/CentOS service config files for doing this would be
> appreciated also.  Thanks!
> 
> --greg
> 
> 
> Gregory A. Fuller - CCNA
> Network Manager
> State University of New York at Oswego
> Phone: (315) 312-5750
> http://www.oswego.edu/~gfuller
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator
> 
> 
> 
> 
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator



NB: 

Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive (www.open.com.au/archives/radiator)?
Have you had a quick look on Google (www.google.com)?
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, MacOS X.
Includes support for reliable RADIUS transport (RadSec),
and DIAMETER translation agent.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.






More information about the radiator mailing list