On Thu, 5 Sep 2002, Adi Linden wrote:
> > > Hi,
> > >
> > > Question when a daily usage counter is setup using this:
> > >
> > > #
> > > counter daily {
> > > filename = ${logdir}/db.counter
> > > key = User-Name
> > > count-attribute = Acct-Session-Time
> > > reset = daily
> > > counter-name = Daily-Session-Time
> > > check-name = Max-Daily-Session
> > > allowed-servicetype = Framed-User
> > > cache-size = 5000
> > > }
> > >
> > >
> > > How can I manually reset someones time without increasing the maximum
> > > daily time for the user?
> >
> > You can't unless you write some c/perl program to play with the gdbm file
>
> That's what I figures, fair enough.
>
> > > It seems like the radius server doesn't reset the maximum daily time if
> > > the user stays connected for more than a day (we have schools with dialup
> > > that use the phone similar to a leased line).
> >
> > That's quite impossible. The gdbm counter file gets wiped out every time the
> > counters are reset.
>
> So is the gdbm file updated every second for every user or is the session
> time written to the file when a stop occured?
>
> > > How can I fix that? Here's
> > > the log from an account that exceeded their time:
> > >
> > > UserName Start_Date_and_Time Stop_Date_and_Time_ Secnds TotSecnd IP-Address_____
>Pt___ Sess-ID__ KB_In_ KB_Out PktIn_ PktOut CallerID__
> > > kihslac 2002/09/01 16:13:44 2002/09/01 16:59:17 2734 2734 216.26.102.78
> 11 3D7278A934D2 406 2290 4228 3570
> > > kihslac 2002/09/01 22:11:40 2002/09/01 22:54:31 2572 5306 216.26.102.78
> 11 3D72D6C5411B 702 3710 6242 6496
> > > kihslac 2002/09/02 11:08:50 2002/09/02 11:13:49 300 5606 216.26.102.78
> 11 3D738CD00264 26 209 367 294
> > > kihslac 2002/09/03 11:44:44 2002/09/03 11:45:18 34 5640 216.26.102.71
> 4 3D74DD9F1A8E 0 0 7 4
> > > kihslac 2002/09/03 12:19:25 2002/09/03 12:20:07 43 5683 216.26.102.71
> 4 3D74E71E1B00 0 0 11 4
> > > kihslac 2002/09/03 12:22:13 2002/09/03 12:41:30 1158 6841 216.26.102.71
> 4 3D74EFA11E2F 32 0 391 3
> > > kihslac 2002/09/03 12:59:36 2002/09/03 13:42:51 2595 9436 216.26.102.71
> 4 3D74F44A2007 440 0 4307 3
> > > kihslac 2002/09/03 13:48:48 2002/09/03 16:06:54 8287 17723 216.26.102.71
> 4 3D7502AC2163 470 0 3375 8
> > > kihslac 2002/09/03 16:16:40 2002/09/03 18:19:42 7382 25105 216.26.102.71
> 4 3D75246E2540 648 1 3400 34
> > > kihslac 2002/09/03 18:35:15 2002/09/03 21:17:23 9729 34834 216.26.102.71
> 4 3D75438E2856 4 0 63 16
> > > kihslac 2002/09/03 23:03:48 2002/09/05 06:55:52 114725 149559 216.26.102.71
> 4 3D757B492C64 6183 7 37710 162
> > >
> > > As the last line indicates, the remote user logged in 2002/09/03 and
> > > didn't disconnect until 2002/09/05 (today). Radius now refuses login on
> > > the grounds of exceeded daily limit, even though the daily limit hasn't
> > > technically been exceeded...
> >
> > If your Max-Daily-Session for this user is smaller than 06:55:52 then he *has*
> > technicaly exceeded his daily limit. He has used your resources today for more
> > time than he is allowed.
> > >
> > > This could be a glitch where the session wasn't properly terminated. The
> > > RAS box (Linux with portslave) improperly shutdown around that time.
> > >
> > > Any suggestions?
> >
> > What is the Max-Daily-Session for this user?
>
> The Max-Daily-Session for this user is 86400. I set it to 200000 and now
> he is able to log back in.
>
> Adi
OK, someone inserted a stupid bug in rlm_counter. Instead of checking for the
Acct-Session-Time it was checking if the attribute type was date. Now all should
work just fine. Just do a cvs update on the rlm_counter module.
--
Kostas Kalevras Network Operations Center
[EMAIL PROTECTED] National Technical University of Athens, Greece
Work Phone: +30 10 7721861
'Go back to the shadow' Gandalf
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
