[RADIATOR] Renew Radiator configuration

[Remco van Noorloos]

Heikki,

Thanks again for you message.

I am already retrieving the RADIUS clients from an SQL database with appropriate function. I'm using the SQLRADIUS AuthBy as well but what I basically want is exactly the same functionality for LDAP2 (something like an SQLLDAP2 AuthBy). 

If we have this feature we would be able to get all details needed dynamically on-request from the database. In this way we don't need the config renew-option anymore.

Thanks,
Remco

-----Oorspronkelijk bericht-----
Van: Heikki Vatiainen [mailto:hvn at open.com.au] 
Verzonden: donderdag 14 april 2011 13:43
Aan: Remco van Noorloos
CC: radiator at open.com.au
Onderwerp: Re: [RADIATOR] Renew Radiator configuration

On 04/13/2011 03:26 PM, Remco van Noorloos wrote:

> Currently I have to restart Radiator to enable config changes. Since
> I'm using it in a test environment at the moment this is no big deal.
> I'd like to use it in a production environment and I don't want
> Radiator to become offline (not even a couple of seconds), so I was
> trying to figure out how to reload the configuration in runtime.

Reloading everything is not possible without restart or SIGHUP.

There are a couple of things that work around this.

Supported directly by Radiator:
- clients (NASes) can be in SQL or LDAP
- realms for proxying can be in SQL or LDAP

This has been very useful in some cases. You can for example, control
debugging so that when NAS information is fetched from SQL, a debugging
flag enables tracing for all requests from that NAS. When this is no
more needed, the flag can be set off, and the next NAS refresh from SQL
turns debugging off.

Supported via <Monitor> clause:
- dynamically settings some variables
- monitoring requests and other stats

Note: if you save Radiator config from Radar, the config will look much
different than it was. Make a backup first.

Supported via hooks:
- create a hook that e.g., consults a file or db
- the hook changes the settings

The hook method may be useful for some cases. The hooks can e.g.,
monitor files or do database hooks and can register their own timers for
periodic tasks.

Last, but not least:
- Radiator is quick to start and restart.

> In the documentation there's something about a SIGHUP signal which
> can be send to make Radiator reload the configuration. There's a
> problem though, I'm using Radiator on a Windows platform which
> doesn't support SIGHUP signals (or any signal at all) as far as I
> know.
> 
> Is there another way to make Radiator reloads it's config in
> runtime?

Hopefully what I listed above has something you could utilise.

Yours,
Heikki

-- 
Heikki Vatiainen <hvn at open.com.au>

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
NetWare etc.