Hi
We are using your WinCap utility (ver 2.3) on our Windows 2000 Advanced
Server machine. There are some time stamp related issues with the packet
sniffing.
We see that the time stamp is not the same as the system time. In one
sequence, the time stamp on the packet is sometimes 12:06 ( the actual
system time ) , and the very next packet has the time stamp of 17:16 ( this
happens at random ). We are unable to find out what the problem is.
I would greatly appreciate it if you could point out the exact manner in
which this information is being captured by packet.dll/wpcap.dll . Could you
give me some pointers on looking at your code directly to trace the problem
and find a solution ?
We have contacted you earlier in this regard - please find attached
correspondence.
Thanks,
Have a nice day,
Regards
Ramya Srinivasan
Systems Engineer - EAI
Intel Technologies
28 Cubbon Road
Bangalore - 560001
Inet : 8-262-3218
Ph : (011)91-80-2869330 Extn - 3218
<<Re: [WinPcap-bugs] Timestamp problems with WinCap - Urgent !>>
--- Begin Message ---
----- Original Message -----
From: "Pandita, Ravi" <[EMAIL PROTECTED]>
To: "'Gianluca Varenni'" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; "Srinivasan, Ramya"
<[EMAIL PROTECTED]>
Cc: "Pandita, Ravi" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, May 06, 2002 7:42 PM
Subject: RE: [WinPcap-bugs] Timestamp problems with WinCap - Urgent !
> Hi Gianlica,
>
> We are using WinPcap 2.3, nevertheless it starts up fine and it has not
> caused and issues on the server. The timestamp problem also appears on
> machines with single processors.
So it's a SMP machine! I don't know why the driver loads (it must not
load!), however, do it at your own risk (we are not responsible if the
machine crashes and/or captures are not correct).
Regarding the timestamp problems even on uniprocessor machines, I don't know
(we never saw this behaviour on our machines). If I have time, tomorrow I'll
create a debug version of the driver to send you, but I cannot guarantee it.
GV
>
> Ravi Pandita
> EBC SAE
> EAI/B2B Cap Plan Mgmt
> PM
> FES and HR projects
>
>
> -----Original Message-----
> From: Gianluca Varenni [mailto:[EMAIL PROTECTED]]
> Sent: Monday, May 06, 2002 10:18 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Cc: Pandita, Ravi; [EMAIL PROTECTED]
> Subject: Re: [WinPcap-bugs] Timestamp problems with WinCap - Urgent !
>
>
> Hi.
>
> What version of WinPcap are you using? It is 2.2. Isn't it?
>
> Inferring from your mail, it's a SMP machine (4 procs). If so, as clearly
> stated on our website, WinPcap does NOT support SMP machines. WinPcap 2.2
> seems to work, but results can be incoherent, and WinPcap can cause BSODs
> (blue screens).
> WinPcap 2.3 has a check that prevents the loading of the driver on SMP
> machines.
>
> If this is not your case, please report the problem as stated at
> http://winpcap.polito.it/contact.htm (bottom half of the page).
>
> GV
>
>
> ----- Original Message -----
> From: "Srinivasan, Ramya" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Cc: "Pandita, Ravi" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Tuesday, April 30, 2002 11:54 PM
> Subject: [WinPcap-bugs] Timestamp problems with WinCap - Urgent !
>
>
> > Hi
> >
> > We are using your WinCap utility on our Windows 2000 Advanced Server
> > machine. There are some time stamp related issues with the packet
> sniffing.
> > We see that the time stamp is not the same as the system time. In one
> > sequence, the time stamp on the packet is sometimes 12:06 ( the actual
> > system time ) , and the very next packet has the time stamp of 17:16 (
> this
> > happens at random ). We are unable to find out what the problem is.
> >
> >
> > Please find attached the output of the windump.exe utility which we ran
on
> > the server today.
> > <<windumpfiles.zip>>
> >
> > We would greatly appreciate it if you could get back to us in 24 hours.
> This
> > is necessary for a critical project here.
> >
> > Here are the details required by you with regard to the system :-
> >
> > System Details :-
> >
> >
> > OS Name Microsoft Windows 2000 Advanced Server
> > Version 5.0.2195 Service Pack 2 Build 2195
> > OS Manufacturer Microsoft Corporation
> > System Name FMSTC2K9012
> > System Manufacturer COMPAQ
> > System Model PROLIANT
> > System Type X86-based PC
> > Processor x86 Family 6 Model 7 Stepping 3 GenuineIntel ~550 Mhz
> > Processor x86 Family 6 Model 7 Stepping 3 GenuineIntel ~550 Mhz
> > Processor x86 Family 6 Model 7 Stepping 3 GenuineIntel ~550 Mhz
> > Processor x86 Family 6 Model 7 Stepping 3 GenuineIntel ~550 Mhz
> > BIOS Version 12/08/99
> > Windows Directory C:\WINNT
> > System Directory C:\WINNT\System32
> > Boot Device \Device\Harddisk0\Partition2
> > Locale United States
> > Time Zone Pacific Daylight Time
> > Total Physical Memory 2,096,668 KB
> > Available Physical Memory 1,332,440 KB
> > Total Virtual Memory 8,242,752 KB
> > Available Virtual Memory 6,376,040 KB
> > Page File Space 6,146,084 KB
> >
> >
> > Adapter Names :-
> >
> > 1.\Device\Packet_{280DDCE0-F928-43BB-B529-0F15EF7C65C7}
> > (Compaq Ethernet/FastEthernet or Gigabit NIC)
> > 2.\Device\Packet_NdisWanIp (NdisWan Adapter)
> >
> >
> > Waiting for a timely response from you
> > Regards,
> > Ramya
> >
>
>
--- End Message ---
