No it is *not* a RADIUS bug

MegaZone (megazone@livingston.com)
Fri, 17 May 1996 09:38:19 -0700 (PDT)

Once upon a time Steve Van Natta shaped the electrons to say...
>Wed Jan 3 07:53:12 1996
>Acct-Status-Type = Start
>
>Wed Jan 3 15:01:01 1996
>Acct-Status-Type = Stop
>Acct-Session-Time = 25673
>
>You list the total seconds as 25673. However when you subtract the
>entry in the stop log, from the entry in the start log, you have a
>total of 25428 seconds or 7:03:48. (HH:MM:SS)

What was the value of Acct-Delay-Time?

>course of logins over the period of a month, this can really add up. The
>biggest embarrasment though would be to release statistics of start and stop
>times in an itemized listing, like the one shown above, that don't match.

The Start and Stop times are stamped by the RADIUS server when it gets
the packet. It may have a substantial delay considering network performance
and server load.

>I believe this is an error, since it doesn't always happen. Sometimes the
>stuff adds up.

No, this is normal, expected behavior.

>If for some reason this isn't an error, which is correct? Your start and
>stop time stamps? Or your total seconds under Acct-Session-Time? We

The value under Acct-Session-Time is the time the user actually used as
tracked by the PortMaster. That is the time you should use for billing.

>accordingly. If you release a bug fix for this soon, however, we won't have
>to change our source code at all.

It isn't a bug.

-MZ

--
Although I work for Livingston Enterprises Technical Support, I alone am
responsible for everything contained herein.  So don't waste my managers'
time bitching to them if you don't like something I've said.  Flame me.
Phone: 800-458-9966  support@livingston.com  <http://www.livingston.com/> 
FAX: 510-426-8951    6920 Koll Center Parkway #220, Pleasanton, CA 94566