ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Ethereal-dev: Re: [Ethereal-dev] Time stamp FT_ values

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Guy Harris <gharris@xxxxxxxxx>
Date: Sun, 20 Jun 2004 18:39:20 -0700
On Mon, Jun 21, 2004 at 10:13:25AM +1000, Ronnie Sahlberg wrote:
> I think it should present it as seconds  if the number is <60 seconds,
> as Minutes and Seconds if it is less than 1 hour,
> etc.

I.e., do what "time_secs_to_str_buf()" does.

> For relative 64bit timestamps I think we need to overload the BASE_xxx field

I think it's already overloaded in some places, so that's reasonable.

> so that we can describe
> BASE_USTIME (come up with better name):
>     1 a guint32 for secs
>     2 a guint32 for usecs
> BASE_NSTIME
>     ditto as above but takes the second 32bit field as nsecs.
> BASE_NDR
>     for a 64 bit value holding the 64bit value that represents the number of
> ticks used for DCERPC (==windows)
>     ticks.   I think it is something like number of x ns .   This is a true
> 64 bit field and not 2 32 bit fields as above is.
> and there are other types of 64 bit timestamps/deltas as well.
> BASE_TIMET
>    which would be a single 32bit integer
> 
> Why not generalize it a bit more and also support even weirder ones such as
> All the older types of timestamps/deltas used by DOS/Windows(old dialects)
> like the weird one where timedeltas are specified in units of 2 seconds
> etc...

...and 32-bit milliseconds, etc.