COA Triggers: customers are not being disconnected

    The way that Radius works is to check access and apply limitation on login, once a customer logged in the only interaction from there is to report the users data, uptime etc if accounting is enabled but by default it will not kick users off or apply any plan changes until the user logs in next.
    Disconnecting customers is achievable but there are 2 main steps you will need to do.

    Access plan configuration:

    The first step is to set up the access plan correctly, you will need to log into duxadmin and open up an access plain you would like to have COA enabled on, under the Extra subheading you will see an option for session terminate by Coa Triggers you willneed to set this to enabled and it is suggested to select the inhibit legacy attributes option.
    From there you will be able to select what triggers you would like to use to close a customers session:


    Router configuration:

    once the plan has been set up the last step is to enable it on the router, on Mikrotik system you will need to go to the radius menu from the main menu on the left hand side, from there you will need to click on the incoming button and simply tick accept then hit the ok button


    If you only have the private IP address for the radius it is also suggested to add the public address ( 203.175.179.9 if you are connecting through mel ) as well since the router will not accept any incoming messages from radius servers that are not listed here, you do not need to select any service but you will need to set the secret :)



    Published