Please see the below.
------------------------------------------------------------------------- http://wiki.mikrotik.com/wiki/Manual:RADIUS_Client Change of Authorization RADIUS disconnect and Change of Authorization (according to RFC3576) are supported as well. These attributes may be changed by a CoA request from the RADIUS server: - Mikrotik-Group - Mikrotik-Recv-Limit - Mikrotik-Xmit-Limit - Mikrotik-Rate-Limit - Ascend-Data-Rate (only if Mikrotik-Rate-Limit is not present) - Ascend-XMit-Rate (only if Mikrotik-Rate-Limit is not present) - Mikrotik-Mark-Id - Filter-Id - Mikrotik-Advertise-Url - Mikrotik-Advertise-Interval - Session-Timeout - Idle-Timeout - Port-Limit Note that it is not possible to change IP address, pool or routes that way - for such changes a user must be disconnected first. ------------------------------------------------------------------ So you could send a disconnect when they hit limit or change authorisation to set rate limit to something really small. If this isn't working a capture of someone crossing the rate limit and the COA / POD may allow others or myself to help diagnose (please also include a sanitised config showing the relevant areas and a network diagram to help understand anything specific in your setup) Regards Alexander Alexander Neilson Neilson Productions Limited [email protected] 021 329 681 On 17 March 2016 at 16:24, JAHANZAIB SYED <[email protected]> wrote: > Thanks for the reply. I am testing now on 6.x with same issue, > Any example? > > > From: [email protected] > > Date: Thu, 17 Mar 2016 16:21:27 +1300 > > To: [email protected] > > Subject: Re: [Mikrotik] mikrotik with freeradius Quota exceed auto > disconnection not working > > > > 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 <[email protected]> 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: [email protected] > > >> To: [email protected] > > >> 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 > > >>> [email protected] > > >>> http://mail.butchevans.com/mailman/listinfo/mikrotik > > >>> > > >>> > > >>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik > > >>> RouterOS > > >> > > >> > > >> _______________________________________________ > > >> Mikrotik mailing list > > >> [email protected] > > >> 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 > > > [email protected] > > > http://mail.butchevans.com/mailman/listinfo/mikrotik > > > > > > Visit http://blog.butchevans.com/ for tutorials related to Mikrotik > RouterOS > > _______________________________________________ > > Mikrotik mailing list > > [email protected] > > 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/a62a307f/attachment.html > > > _______________________________________________ > Mikrotik mailing list > [email protected] > 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/b29e43e2/attachment.html> _______________________________________________ Mikrotik mailing list [email protected] http://mail.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
