SQL Counter Module
The sqlcounter
module provides a general framework to allow access
based on accumulated usage of a resource, such as total time online in
a given period, total data transferred in a given period, etc. This is
very useful in a Prepaid Service situation, where a user has paid for
a finite amount of usage and should not be allowed to use more than
that service. Collection, monitoring, and replenishment of prepaid
services are beyond the scope of this module.
Rather than maintaining separate (GDBM
) databases of accounting info
for each counter, this module uses the data stored in the radacct
table
by the sql
modules.
This module NEVER does any database INSERTs or UPDATEs. It is totally
dependent on the SQL module to process Accounting packets.
|
Syntax
Configuration explanation.
- sql_module_instance
-
Holds the instance of the
sql
module to use when querying the SQL database.
Normally it is just sql . If you define more and one SQL module instance
(usually for failover situations), you can specify which module has access to
the Accounting Data (radacct table ).
|
- reset
-
Defines when the counters are all reset to zero.
It can be hourly
, daily
, weekly
, monthly
or never
.
It can also be user defined as the form: num[hdwm]
where:
Parameter | Description |
---|---|
|
hours |
|
days |
|
weeks |
|
months |
If the latter is omitted days will be assumed.
In example:
-
reset
= 10h (reset every 10 hours) -
reset
= 12 (reset every 12 days)- key
-
Specifies the unique identifier for the counter records (usually
User-Name
).
The query
parameter specifies the SQL query used to get the current Counter value
from the database.
- reset_period_start_name
-
The name of the attribute which is used to store the time that the current reset period started.
The default is &control.${.:instance}-Start
Note because we are counting seconds, this attribute is of type uint64
, and not date
.
- reset_period_end_name
-
The name of the attribute which is used to store the time that the current reset period will end.
The default is &control.${.:instance}-End
Note because we are counting seconds, this attribute is of type uint64
, and not date
.
- counter_name
-
Name of the
check
attribute to use to access the counter in theusers
file or SQLradcheck
orradgroupcheck
tables.
After the sqlcounter module has run, the counter attribute will exist.
Default Configuration
# sqlcounter <name> {
# sql_module_instance = sql_foo
# reset = 12h
# key = "%{&Stripped-User-Name || &User-Name}"
# if (&control.Daily-Session-Time > 3600) {
# &Reply-Message := "You've used up more than one hour today"
# reject
# }
sqlcounter dailycounter {
sql_module_instance = sql
dialect = ${modules.sql.dialect}
# reset_period_start_name = &control.${.:instance}-Reset-Start
# reset_period_end_name = &control.${.:instance}-Reset-End
counter_name = &control.Daily-Session-Time
check_name = &control.Max-Daily-Session
reply_name = &reply.Session-Timeout
key = "%{&Stripped-User-Name || &User-Name}"
reset = daily
$INCLUDE ${modconfdir}/sql/counter/${dialect}/${.:instance}.conf
}
sqlcounter monthlycounter {
sql_module_instance = sql
dialect = ${modules.sql.dialect}
counter_name = &Monthly-Session-Time
check_name = &control.Max-Monthly-Session
reply_name = &reply.Session-Timeout
key = &User-Name
reset = monthly
$INCLUDE ${modconfdir}/sql/counter/${dialect}/${.:instance}.conf
}
sqlcounter noresetcounter {
sql_module_instance = sql
dialect = ${modules.sql.dialect}
counter_name = &Max-All-Session-Time
check_name = &control.Max-All-Session
key = &User-Name
reset = never
$INCLUDE ${modconfdir}/sql/counter/${dialect}/${.:instance}.conf
}
sqlcounter expire_on_login {
sql_module_instance = sql
dialect = ${modules.sql.dialect}
counter_name = &Expire-After-Initial-Login
check_name = &control.Expire-After
key = &User-Name
reset = never
$INCLUDE ${modconfdir}/sql/counter/${dialect}/${.:instance}.conf
}