[RADIATOR] Timestamp question

[Jose Borges Ferreira]

Hi!

Acct-Delay-Time is normally 0 and only used when a retry happen. It is,
usually, the difference in seconds between the time the packet is sent and
when the packet should be sent.

So if your NAS retries every 30 seconds you should have:
Acct-Delay-Time = 0 on the first packet
Acct-Delay-Time = 30 on the first retry
Acct-Delay-Time = 60 on the second retry and so on

Given this TimeStamp-Acct-Delay-Time gives you the time corrected timestamp.


José Borges Ferreira

Johnny Carson  - "I was so naive as a kid I used to sneak behind the barn
and do nothing."

On Fri, Feb 6, 2009 at 11:44 PM, Robert Blayzor <rblayzor.bulk at inoc.net>wrote:

> On Feb 6, 2009, at 5:53 PM, Hugh Irvine wrote:
>
>> The attribute "Timestamp" is added to incoming accounting requests by
>> Radiator and is the time on the Radiator host, corrected by the
>> "Acct-Delay-Time".
>>
>
>
>
> Ok this is interesting then.  I have a NAS at one location (and only one
> that I can tell) that seems to be generating RADIUS records that are DAYS
> behind.  It's not the server because I see several other clients with
> accurate time.  How is acct-delay-time determined?  Before I get into packet
> debugging I"m trying to figure out exactly why this might be happening.
>
>
> --
> Robert Blayzor, BOFH
> INOC, LLC
> rblayzor at inoc.net
> http://www.inoc.net/~rblayzor/ <http://www.inoc.net/%7Erblayzor/>
>
>
>
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20090207/0c13ce11/attachment.html>