Ethereal-dev: Re: [Ethereal-dev] NetXray / Sniffer Time Codes [Fwd: NetXRay timing base]
The capture was done with some version of Sniffer Pro
Jason House wrote:
>
> Shortly after discovering some timing problems with Ethereal and
> NetXray, I tried to verify the timing factors listed. Unfortunately,
> the supplied correction factors were still off by about 10 seconds per
> day. Calculations yielded a value of 0.8382229. Currently I don't know
> much about what it was captured with other than "It was captured on a
> Dolch machine running Windows ??" A filtered portion of the capture
> file is attached.
>
> ------------------------------------------------------------------------
>
> Subject: Re: NetXRay timing base
> Date: Thu, 08 Feb 2001 14:52:47 -0500
> From: Shawn Duffalo <sduffalo@xxxxxxxxx>
> Organization: The MITRE Corporation
> To: Jason House <jhouse@xxxxxxxxx>
> References: <3A8159CD.2FABDF04@xxxxxxxxx>
>
> the factor appears to always be 0.8382229, which is about 10 sec per day off of
> the numbers you have below. not sure i know why but it would get close enough
> for any analysis we would want to do
>
> Jason House wrote:
> >
> > There are two candidate bases in the mailings sent out.
> > A numerical based estimate is 88/105 (=.8380952...) correction factor.
> > Another guess is .838096. That number is based on similarity to
> > something else...
> >
> > I don't expect you to differentiate the two, just see if what you have
> > appears to match. The two estimates will diverge from each other by a
> > second on a 2 week capture file.
>
> ------------------------------------------------------------------------
>
> Shawn Duffalo <sduffalo@xxxxxxxxx>
> Systems Engineer
> MITRE Corporation
> W072
>
> Shawn Duffalo
> Systems Engineer <sduffalo@xxxxxxxxx>
> MITRE Corporation
> W072
> 12 Christopher Way Work: 732-389-6542
> Eatontown
> NJ
> 07724
> Additional Information:
> Last Name Duffalo
> First Name Shawn
> Version 2.1
>
> ------------------------------------------------------------------------
> Name: NtdrTesting_Dasb_Wed_1803-1859.cap
> NtdrTesting_Dasb_Wed_1803-1859.cap Type: application/x-unknown-content-type-capFile
> Encoding: base64