External accounting script help
aland at deployingradius.com
Tue May 12 21:29:03 CEST 2015
On May 12, 2015, at 2:35 PM, Paul Boehmer <pboehmer at seidata.com> wrote:
> It would be nice if we could do that within the configuration, but I'm trying to figure out how you would handle a scenario like:
> Customer connected to specific VPI/VCI and gets locked out due to billing issue. Customer attempts to bypass by using a different account credentials, though they are still on the same VPI/VCI.
What does that mean? i.e. When you want a user rejected, what's in the Access-Request?
> On the XtRadius system we are migrating from, we log which customers are on which VCI/VPI and if there is a User-Name conflict at some point, an email is sent to the administrators with notification of the conflict. Keep in mind that this configuration has been in use since early 2000 and has various other support programs that depend on the output of the exec scripts. Not pretty, but it worked. Ideally, we will be moving from flat text files to SQL, but this will be in baby steps.
This is typically what you should use databases for. Create a table of User-Name, and VPI / VCI. Then, check that the User-Name and VPI/VCI in the request match the User-Name and VPI/VCI in the database.
More information about the Freeradius-Users