Yes in the default file. Dailycounter automatically sets the session timeout so once user's session is expired, user is not allowed to login this is all already happening with default config. As far as data coa is concerned you have to read accounting packets using unlang in accounting section in default file of course and send a coa when the data limit is reached! Hope this helps. BR, Anirudh Malhotra 8zero2 Mail: 8zero2.in@gmail.com Facebook: www.facebook.com/8zero2 Twitter: @8zero2_in Blog: blog.8zero2.in On 21 Feb 2016, 14:19 +0530, Oscar Jofre<oscar@jofre.com>, wrote:
Hi,
You put "update coa" in an authorize section or an accounting section.
On sites-available/default ?
It is possible to send CoA only when user is over limit session ? I mean how to join with dailycounter ?
-----Mensaje original----- De: Freeradius-Users [mailto:freeradius-users-bounces+oscar=jofre.com@lists.freeradius.org] En nombre de Alan DeKok Enviado el: domingo, 21 de febrero de 2016 0:22 Para: FreeRadius users mailing list Asunto: Re: Modules - dictionary
On Feb 20, 2016, at 6:18 PM, Oscar Jofre<oscar@jofre.com>wrote:
See the NAS documentation. If it supports CoA-Request or Disconnect-Request packets, yes. Read raddb/sites-available/originate-coa.
I've read the documentation but I don't understand where to activate CoA to send Disconnect-Request, on originate-coa:
You put "update coa" in an authorize section or an accounting section.
I think I should add more data into update coa according to mikrotik documentation:
If that's what Mikrotik wants, I guess so.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html