mysqlRadius is a web application that handles from one to hundreds of the tried and proven Cistron 1.6.6 RADIUS server. A MySQL database is used for all application and configuration data and ultimately used for configuring all the mysqlRadius controlled RADIUS servers.
In a nutshell, mysqlRadius is in charge of administering the following 5* files that can be as much on a local server as on a remote one. For example, if the raddb directory is in its mysqlRadius default location then these would be the 5* files:
/usr/local/etc/raddb/users
/usr/local/etc/raddb/clients
/usr/local/etc/raddb/naslist
/usr/local/etc/raddb/naspasswd
/usr/local/etc/raddb/realms (*Not yet but soon in 2.x series)
mysqlRadius also supports any type of RADIUS profiles that the Cistron radiusd supports by means of configurable and unlimited number of different templates (see mysqlRadius.tProfile and mysqlRadius.tProfileName.) These templates can be a default profile for all servers or be specified for each server and/or each user (and also if they are meant for CHAP or PAP.) It is also possible for the profile template system to be used creatively, for example in implementing advanced profiles like:
Calling-Station-Id (caller-id is used along with the user and passwd) for authentication.
Special DEFAULT per realm profiles for RADIUS proxy servers. (For proxy functionality see the raddb/realms file -you will have to edit it yourself in the mysqlRadius 1.X series.)
What mysqlRadius is not
mysqlRadius is not patch of Cistron, nor depends on a RADIUS server that connects directly* to a MySQL database for authentication.
Experience has demonstrated that it is better to have static archives for servers in production status. This design facilitates the boot sequence and offers an extra backup of mission critical archives -also making migrations and clustering very simple.
...
*The related application mysqlRadacct uses a slighly altered version of the Cistron 1.6.6 RADIUS server -see next section- that enables it to store accounting data in what is usually a central data base -or mysql cluster- (this provides failover when using multiple backup RADIUS servers.) Our modified version of Cistron also can run SMTP-AFTER-AUTH in conjuntion with our mysqlSendmail mysqlISP subsystem (please note that mysqlISP subsystems also can work as complete standalone applications.) Furthermore, we also have a modified version of the highly regarded Qualcomm (tm) qpopper that also can implement SMTP-AFTER-POP also in conjuntion with our mysqlSendmail application.