Are you configured to send COA or POD from the radius server once the limit is 
reached?

I understand Mikrotik may have published a new dictionary for radius to reflect 
changes they have made  

IIRC they used to allow only POD and no COA but now support COA as well. This 
may allow you to make it work on 6.34 but not in V5. 

Also maybe check if you have these signals configured with a capture to ensure 
they are sent across. 

Regards
Alexander

> On 17/03/2016, at 16:04, JAHANZAIB SYED <aaca...@hotmail.com> wrote:
> 
> Testing it on Mikrotik 5.20 and 6.34.x
> Same issue that user dont get auto disconnect when quota reaches limit. 
> [however they get access denied on there next login]
> 
> 
>> Date: Wed, 16 Mar 2016 08:34:38 -0400
>> From: spie...@avolve.net
>> To: mikrotik@mail.butchevans.com
>> Subject: Re: [Mikrotik] mikrotik with freeradius Quota exceed auto 
>> disconnection not working
>> 
>> What version of Mikrotik?
>> 
>>> On Wed, March 16, 2016 6:16 am, JAHANZAIB SYED wrote:
>>> I am using Mikrotik with FREERADIUS 2.x. Radius Incoming is enabled with
>>> port 1700.
>>> 
>>> My problem is that after user reaches his quota limit , he does not gets
>>> disconnect automatically. If I disconnect him myself and he try to
>>> reconnect then he gets access denied. how this disconnection can be made
>>> automatically?
>>> 
>>> Using following sql counter.
>>> 
>>> 
>>> sqlcounter totalbytecounter { counter-name = Mikrotik-Total-Limit
>>> check-name = Mikrotik-Total-Limit reply-name = Mikrotik-Total-Limit
>>> reply-message = "You have reached your bandwidth limit" sqlmod-inst = sql
>>> key = User-Name reset = never query = "SELECT
>>> ((SUM(AcctInputOctets)+SUM(AcctOutputOctets))) FROM radacct WHERE
>>> UserName='%{%k}'"
>>> }
>>> 
>>> 
>>> Also I have defined this under authorize section in
>>> /etc/freeradius/sites-enabled/default
>>> 
>>> 
>>> totalbytecounter
>>> 
>>> Help Please.
>>> 
>>> 
>>> 
>>> 
>>> -------------- next part --------------
>>> An HTML attachment was scrubbed...
>>> URL:
>>> <http://mail.butchevans.com/pipermail/mikrotik/attachments/20160316/4ce02
>>> 42d/attachment.html>
>>> _______________________________________________
>>> Mikrotik mailing list
>>> Mikrotik@mail.butchevans.com
>>> http://mail.butchevans.com/mailman/listinfo/mikrotik
>>> 
>>> 
>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
>>> RouterOS
>> 
>> 
>> _______________________________________________
>> Mikrotik mailing list
>> Mikrotik@mail.butchevans.com
>> http://mail.butchevans.com/mailman/listinfo/mikrotik
>> 
>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
>                         
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://mail.butchevans.com/pipermail/mikrotik/attachments/20160317/74cc3f9f/attachment.html>
> _______________________________________________
> Mikrotik mailing list
> Mikrotik@mail.butchevans.com
> http://mail.butchevans.com/mailman/listinfo/mikrotik
> 
> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://mail.butchevans.com/mailman/listinfo/mikrotik

Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS

Reply via email to