Hi. As far as I know the sqlcounter will disallow furhter authentrication only if the user has used her time limit quota. The Session-Timeout Attribute will kick him out when loged in and the Max-XYZ-Session will be checked the next time a user wants to login. You would need an additional Attribute for user expiration date as well.
On Wed, 11 May 2005 15:07:25 +0700 avudz <[EMAIL PROTECTED]> wrote: > Hello Marcin, > > Wednesday, May 11, 2005, 2:54:09 PM, you wrote: > > MJ> In your case you should change reset=never to reset=1h if you > MJ> want to reset the counter every hour. > MJ> But in that case it would not make sense to call it > MJ> Max-Hour-Session-Time since the counter would be reset after the > MJ> user's time is off and then she would be able to login again... > > > --- ups, sorry. thanks for correcting my mistake. > > > MJ> What do you exactly wanna do? Your config as it is now does not make any > sense. > MJ> Your SQL says you want to allow your users to stay on 24 > MJ> hours a day. But then you want to reset the counter every hour? > MJ> That would make sense if the reset value was greater than the > MJ> corresponding value of your Max-XYZ-Session. > > --- in my case, i have 1 day voucher limited to 24 hour, the > password will expire next day after first login even the user only use 3 > hours. > > > > > > -- > Best regards, > avudz > > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
