[Winpcap-users] MODE_STAT

Gianluca Varenni gianluca.varenni at cacetech.com
Wed Dec 12 23:07:06 GMT 2007


Uh... that's *really* good to hear!

I was really worried of having to yell for days and days trying to reproduce 
the issue :-)

Thanks for the update
GV



----- Original Message ----- 
From: "Fitt, Jonathan" <Jonathan.Fitt at anritsu.com>
To: <winpcap-users at winpcap.org>
Sent: Wednesday, December 12, 2007 2:35 PM
Subject: RE: [Winpcap-users] MODE_STAT


> Aha!
>
> I noticed that it was happening on a rough 1 second repetition.
> I found that the way I was dealing with tv_sec and tv_usec was not
> correct. I was padding zeros form the wrong end so that when tv_usec was
> less than 100000 instead of seeing 0.004444 seconds I was seeing
> 0.444400!
>
> Mystery solved. User error.
>
> Thanks for your help Gianluca.
>
> Jon
>
> -----Original Message-----
> From: Fitt, Jonathan
> Sent: Tuesday, December 11, 2007 3:41 PM
> To: 'winpcap-users at winpcap.org'
> Subject: RE: [Winpcap-users] MODE_STAT
>
> Thanks a lot. It is really strange, and it's causing us a lot of
> headaches!
> It only seems to occur with read timeouts of less than 1000ms.
>
> Thanks again,
>
> Jonathan
>
> -----Original Message-----
> From: winpcap-users-bounces at winpcap.org
> [mailto:winpcap-users-bounces at winpcap.org] On Behalf Of Gianluca Varenni
> Sent: Tuesday, December 11, 2007 2:37 PM
> To: winpcap-users at winpcap.org
> Subject: Re: [Winpcap-users] MODE_STAT
>
> Clearly speaking, that jitter in the header time is not normal at all.
> It can happen on a dual core/hyperthreaded or multiprocessor machine,
> but it should not happen on a single processor machine like the one you
> have.
> I need to investigate the issue, but it might take some time.
>
> Have a nice day
> GV
>
> _______________________________________________
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-users 



More information about the Winpcap-users mailing list