SQL Counter access period reply CoA on Update Interim

[Jose Luis Espinoza]

Thanks Again Alan for your time. Problem is solved.. Adding Session-Timeout on radreply works!

JL

> El 9/6/2015, a las 17:50, Alan DeKok <aland at deployingradius.com> escribió:
> 
> On Jun 9, 2015, at 4:45 PM, Jose Luis Espinoza <info at ispcube.com> wrote:
>> Using Mikrotik as NAS. My main goal is to get users disconnected after some condition during acct update process.
> 
>  That's not what you said in your first message.
> 
>> In radcheck table I have
>> 
>> ZmeG0   Access-Period    := 120
> 
>  With the sqlcounter module, that will send Session-Timeout of 120.  Which is very, very, low.  The NAS is free to ignore such a low value.
> 
>  It should be 5 minutes or more.
> 
>  And, the Session-Timeout will be sent during the initial Access-Request.  It will have NO EFFECT on later Accounting-Request packets.
> 
>> then in NAS I setup acct interim period in 1 minute. 
> 
>  That is probably too often.  But if you want a high-load server, that's up to you.
> 
>> Then when NAS is doing Acct Update
> 
>  Which doesn't send a Session-Timeout attribute back.
> 
>  What happens during an Access-Request packet?
> 
>> I need to mention that I have modified accounting_update_query and accounting_stop_query
> 
>  Uh... if you're going to use non-standard schema && queries, the standard sqlcounter module is likely to not work.
> 
>  If you want to send a CoA packet when the server receives an Accounting-Request packet, see raddb/sites-available/originate-coa.  This is extensively documented.
> 
>  Alan DeKok.
> 
> 
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html