[RADIATOR] ClientListSQL question

[Hugh Irvine]

Hello Markus -

Answers below.


On 9 Dec 2009, at 10:28, Markus Moeller wrote:

> Hi,
>  
>  I'd like to put my client settings into a database instead of a flat file, but want to make the system resilient. Can I use two database servers .e.g. a primary and a backup ? If so how ?
>  

You define two sets of DBSource, DBUsername and DBAuth lines, as for any other SQL clause.


> Secondly when I use a refreshperiod > 0 or send a HUP signal to radiator, will Radiator delete the existing client list ONLY once ClientListSQL has successfully read new data ? Otherwise I would have a none functional Radiator server. 
>  

Two different things happen here.

First, a RefreshPeriod will cause Radiator to re-read the database for a new list of clients, but if the database is not contactable the old set of clients is retained.

Second, a HUP signal will re-initialise the Radiator instance completely, so the clients will be purged and if the database is not contactable you will then have a problem.

> Can I also store the TACACSPLUSkey in the SQL database. I didn't see it in the list of attributes.
>  

For an alternative way to deal with client definitions from the database, see "goodies/sqlclienthook.pl".

regards

Hugh


> Thank you
> Markus
> _______________________________________________
> 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.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.