External accounting script help

[Paul Boehmer]

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.

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.

Thanks again for the assistance!


On 05/12/15 14:03, Alan DeKok wrote:
> On May 12, 2015, at 1:35 PM, Paul Boehmer <pboehmer at seidata.com> wrote:
>> No, in the end the script will be checking VPI/VCI ports numbers for conflicts and additional sanity checks.
>
>    You can write most of those checks in "unlang".  That's the policy language included with FreeRADIUS.
>
>    See the many examples in raddb/
>
>    Alan DeKok.
>
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
>
>

-- 
Paul Boehmer