DMA Radius Manager requires a Linux
system which meets the following conditions:
Apache HTTP server is installed
PHP version 4 or better is available with MySQL support
MySQL version 5 or better is available
DMA Radius Manager 4.0
and 4.1 requires a CentOS 5-6 or Ubuntu
10-12 server. DMA Radius Manager 4.2 is compatible
with CentOS 5-6-7 and Ubuntu 10-14 Linux
versions. Older DMA Radius Manager versions can be installed on Fedora Core
8-12, Centos 5-6, Ubuntu 10-12 etc.
We encourage our customers to use
CentOS or Ubuntu operating systems. These
are the most complete Linux systems available nowadays and the installation
of Radius Manager requires only 20-30 minutes (including
the installation of Linux packages).
If You have a non standard Linux distribution,
please contact us before ordering your DMA Radius Manager
If You are using a free RADIUS billing
solution, You have to combine numerous standalone applications to get a complete
working billing system, not mentioning the required time and the knowledge You
need to get it to work.
When You purchase Radius Manager
You will get all the required components in one package at
a very affordable price. And a big difference: if You purchase Radius Manager
system from us, You will not get only the software itself, but You will also
get a free remote installation support! Till now all our customers
have successfully installed Radius Manager system on their Linux servers.
Yes, You can customize the design and
language of the system easily. You have to edit the HTML templates with your
favorite HTML editor and to translate the language files (if they aren't translated
already - read more about the language customization here).
The code and graphical design are fully separated.
Radius Manager is a commercial system
and it comes without source codes. The source codes are proprietary. The subject
of copyright protection and other intellectual property rights are owned by
DMA Softlab LLC.
The first two columns are mandatory,
the remaining are optional. Password must be clear text format (unencrypted).
Be 100% sure there are no duplicate user names exist in the
Enter date in MySQL
format: YYYY-MM-DD. Enabled field can be blank (blank - enabled,
1 - enabled, 0 - disabled). Ipmodecpe field: 0 - NAS, 1 -
RADIUS, 2 - static. Srvid is the internal service id. The
available traffic is defined in Bytes, the
available online time is defined in HH:MM:SS
The import tool is compatible with
the current version of Radius Manager. Old versions are not supported.
There are complete upgrade scripts
included in the distribution archive. You can upgrade your Radius Manager from any older version
to the latest. Downgrading of databases is not possible, so always create a
full database backup before You proceed the upgrade process.
ChilliSpot v 1.1 running
on Linux (downloadable from our site)
and DD-WRT are fully supported by Radius Manager
3.9+, including the auto disconnection function (traffic, online
time and expiration date), multiple NASs, bandwidth limitation etc. All supported
disconnection methods are available: REMOTE and NAS. Please note REMOTE disconnection
method requires a static, routed IP address configured on the Chillispot router's
You can try to configure almost every
RADIUS compatible NAS with Radius Manager. The basic functions will
work in most cases (authentication, accounting), but there is no guarantee
that the special functions will be available (automatic
disconnection, static IP addresses, IP pool selection, remote disconnection
The special features of custom NAS
are controllable with custom RADIUS attributes. A proper
documentation is required in order to define the the attributes in ACP.
Please note, techical support
is available for the officially supported NAS types
Yes, You can. If your NASes are using dynamic
or local IP addresses (which are not reachable directly by the RADIUS server),
realize the following setup to get them working with Radius Manager:
Install a central PPtP server (Mikrotik) in NOC, beside the RADIUS server.
Connect all your NASes (Mikrotik, Cisco) to the central PPtP server with
PPtP connections. The central PPtP server must have public, static IP (it
must be visible for the remote NASes).
PPtP server will assign static local IPs to NASes via PPtP tunnels.
All NASes will reach the RADIUS server via PPtP tunnels and vice versa (RADIUS
Using this method NASes can use any IP (public, local,
static, dynamic) and RADIUS server will see them on local, static IP addresses,
via the PPtP tunnels. Tunnels are used for RADIUS packets only (low traffic),
while the heavy Internet traffic is going through the main connection of NAS
Compare the installed php file sizes
with the archived ones. They must match exactly. ASCII mode FTP transfer corrupts
the IonCube encoded php files. Upload the original tarball to your server and
untar it there:
tar xf [filename]
After that, copy the untarred Radius
Manager PHP files to your WWW folder.
Also, check the content of the lic.txt.
Compare it with the version You've downloaded from our portal.
Check the Apache error log. Maybe You haven't
installed php-mysql or license is not installed or corrupt
/ invalid. Also, if there are PHP memory problems, increase the available memory
size in php.ini from default 8 MB to 16 MB.
Upon accessing Radius Manager ACP, I'm getting the following message:
Fatal error: Allowed memory size of 8388608
bytes exhausted (tried to allocate 140 bytes) in /var/www/radiusmanager/misc.php
on line 0
Define higher memory limit instead of the default
8 MB in php.ini and restart httpd:
memory_limit = 16M ; Maximum
amount of memory a script may consume
NetworkManager service avoids the
normal operation of ionCube runtime system. IonCube requires HTTPD to get
started after the network startup. Disable NetworkManager
service (available on newer Linux variants) and enable Network
at boot time to fix this issue. Use Webmin or shell commands to complete this
IonCube can work with properly configured
ethernet interfaces only. Be sure an IP address is configured
on the licensed ethernet interface (it can be a dummy or
real IP) otherwise blank page will appear instead of Radius
Manager WEB interface.
set sim-use = 1 for any user, only one session can be active for a specific
account in a same time. If there is a communication problem between
the NAS and RADIUS server when the user logs off, the user
will be logged off from the NAS, but RADIUS server will know nothing about
this logoff event. This is why RADIUS thinks the user is already online and
prevents new logins for the same account.
There is a automatic session closing
feature available in Radius Manager. After 10 minutes of
inactivity (no accounting sessions are arrived from the NAS) the session will
be treated as closed and users can log on again with the same name. Be sure
rmpoller is running all the time.
There is a option "Close
session" in ACP / online list which closes the session immediately.
Use it if You don't want to wait for the auto stale session shutdown.
Establish perfect connection between
NAS and Radius server to avoid these problems.
Radius Manager CS license level has
no limitation in the maximal number of users. In live systems only the capacity
of NAS limits the maximal number of concurrent sessions. You can control up
to 600-800 active PPPoE sessions on a 2.4 GHz NAS with Mikrotik
2.9+ OS. This number can be higher on a dual or quad core / multi CPU NAS
systems. Check the CPU load on the NAS to estimate the available capacity.
Where username is your RADIUS user name (it is radius by default)
and password is your MySQL RADIUS password.
In some cases it is necessary to restart MySQL server (if it
reports too many connections) to complete the repair procedure successfully.
It is also recommended to shut down the radiusd process while
the database check is running.
Never shut down your
system uncleanly in order to prevent such errors like this.
Always shut down the Linux system with halt or reboot
command. It is a good idea to always have a backup of the actual RADIUS
database (daily backup).
You can accept PayPal and
CC payments (PayPal Express Checkout) with your merchant
account registered from any of the supported countries. Consult PayPal.com
to determine if You are eligible to register a merchant account or not?
Check the size of logfile /usr/local/var/log/radius/radius.log.
If it has grown too big Linux file system write operations are delayed and
completely slow down the FreeRadius server. In the same time You see many
unfinished RADIUS requests in radius.log.
Another problem can be a slow hard
disk and when a database grows, MySQL server can't store the accounting data
in db tables fast enough. Use fast hard disks. The recommended disks are:
SATA, SCSI, RAID arrays.
Solution 1: Delete
the logfile, restart FreeRadius and install a logrotate script.
Solution 2: Delete
the past years from the radacct table and optimize the MySQL tables. Radacct
cleaner SQL scripts is available in the Radius Manager distribution archive
Complete the following
steps to configure the wireless signal monitoring in Radius Manager:
1. Enable SNMP in AP and set the
SNMP community string
2. Definethe AP in RM ACP and enter the
same community string
The system scans the APs in every 5 minutes. You
have to wait for the results (ACP / online users list) or You can invoke the
poller manually (for testing purposes).
If there is no response, check your network and AP.
You can alse test the SNMP access from Linux shell:
snmpwalk -c public -v 1 IP
Where IP is the IP address of your AP. If there is
a valid response, the AP monitoring should work in Radius Manager.
Be sure the SNMP packages are installed on your Linux
yum install net-snmp net-snmp-utils php-snmp
apt-get install php5-snmp
Only PPPoE and Hotspot authenicated
users can be monitored. The caller ID (ACP / online users
list) must be equal with the MAC address listed in the registration table
in AP. The system is compatible with Mikrotik, Ubiquiti and other SNMP enabled
There is a bug in the latest MySQL server version available
in CentOS 6.x releases. If You uncleanly shut down the system, MySQL server
will not start if /var/lib/mysql/mysql.sock file has not been deleted
manually. The problem can be fixed easily.
1. Delete the file /var/lib/mysql/mysql.sock:
2. Restart mysqld:
service mysqld restart
1. Edit /etc/init.d/mysqld file and comment out
the following block:
#if [ -S "$socketfile" ] ; then
# echo "Another MySQL daemon already running with the same unix socket."
# action $"Starting $prog: " /bin/false
# return 1
Due to unclean system shutdown a stale lockfile has been left
in /tmp directory. Delete the /tmp/wlanpoller.pid and /tmp/cmtspoller.pid
files manually. Wait 10 minutes for the completion of the next poller
cycle. It is strongly recommended to upgrade your system
to version 4.7.0 or higher.