<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Gianluca,<br>
<br>
That delay is important to me because I am sending data from my
detector, so one image is 64 packets, all need to be received to get a
single image. My detector works in different modes, sometimes gets one
image and stops, sometimes sends 1000/s, all of which should be
received. I wanted to use the timeout in WinPCAP to control the
situations when I am waiting for the image in the computer, and it is
not sent from the hardware. Then on a timeout I can tell that there is
no image received and continue operation of my code. Otherwise it keeps
waiting for the image forever, and I have no control to stop that
waiting cycle. Obviously I can put time calls in my receiving procedure
(what I am doing now), but that takes time and slows down me receiving
capabilities in the case of 1000 frames/s, which is very important to
me. The speed of my data acquisition code is very critical and every
extra time check in between calls to image packets slows it down.<br>
<br>
<b>I am very impressed by WinPCAP in general as it allowed me to get
data so fast! No Windows winsock functions come even close to the
performance of WinPCAP. Very glad someone recommended it to me!<br>
<br>
</b>All the best,<br>
<br>
Anton<br>
<blockquote
cite="mid:AF250ADA3E79E64A97672D195AA114E11A4DAE@MAILBOXES.nbttech.com"
type="cite">
<meta http-equiv="Content-Type"
content="text/html; charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Anton,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">I
believe it could be actually some corner case in the logic (inside
WinPcap) that decides when the event needs to be signaled and when it
needs to be reset. If it’s an issue like this, it probably shows up
only in a scenario when the traffic is extremely slow or when you
transmit a fixed amount of packets and then nothing else on the wire.
Out of curiosity, why is this delay so critical to you? This delay
usually causes issues only when you try to retransmit the received
packets on a different interface (like a bridge).<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Have
a nice day<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">GV<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">From:</span></b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">
Anton Tremsin [<a class="moz-txt-link-freetext" href="mailto:ast@ssl.berkeley.edu">mailto:ast@ssl.berkeley.edu</a>] <br>
<b>Sent:</b> Wednesday, March 23, 2011 7:43 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:winpcap-users@winpcap.org">winpcap-users@winpcap.org</a><br>
<b>Cc:</b> Gianluca Varenni<br>
<b>Subject:</b> Re: [Winpcap-users] Winpcap-users Digest, Vol 72,
Issue 8<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Gianluca,<br>
<br>
You are right again, my comment was not correct. I looked at the
timestamps of all 64 packets in Wireshark to answer your question. What
have looked reliable to me first, now shows that there was some delay
in the data receiving sequence, but I cannot tell precisely where that
delay happens (at which packet number) and how long it is (changes from
one data set to another and it is hard to find where the gap is).
Wireshark shows all 64 packets at once, which looked fine as if there
was no delays. <br>
<br>
What is strange in my receiving code now is the following: data comes
with something like 57 - 62 packets, then there is delay equal to the
timeout parameter which I set in the open function. Then the rest of
the data comes. No timeout error shows up in that case. It is only
after the last packet was received the timeout events show up in the
pcap_next_ex() return parameter.<br>
<br>
May be it is all in the card driver and I cannot get any help from
Chelsio support, after describing the situation to them. For now I set
the timeout to 1 ms, and handle many timeout events when I do not have
data coming in. That seems to be not an elegant solution, but somewhat
sufficient for the alpha version of our data acquisition. I am trying
to borrow another card (from different manufacturer) to test whether it
is indeed in the card driver. What puzzles me is why setmintocopy()
does not any effect in my code?<br>
<br>
Thanks,<br>
<br>
Anton<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Anton,</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">You
say that “</span>Wireshark grabs data fast and reliably”. What do you
mean by that? Do you look at the timestamps in wireshark to say that
it’s reliable?<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Have a nice day<o:p></o:p></p>
<p class="MsoNormal">GV<o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"> </span><o:p></o:p></p>
<div>
<div
style="border-style: solid none none; border-color: -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">From:</span></b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">
<a moz-do-not-send="true"
href="mailto:winpcap-users-bounces@winpcap.org">winpcap-users-bounces@winpcap.org</a>
[<a moz-do-not-send="true"
href="mailto:winpcap-users-bounces@winpcap.org">mailto:winpcap-users-bounces@winpcap.org</a>]
<b>On Behalf Of </b>Anton Tremsin<br>
<b>Sent:</b> Wednesday, March 16, 2011 9:24 AM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:winpcap-users@winpcap.org">winpcap-users@winpcap.org</a><br>
<b>Subject:</b> Re: [Winpcap-users] Winpcap-users Digest, Vol 72,
Issue 8</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Hi Akif,<br>
<br>
I have not tried packet.h, but I see the same behavior: Wireshark
grabs data fast and reliably, while my code using C library has those
delays, which I cannot get rid of. I can receive ~55 packets (8K each)
reliably, with no any delays, but for 64 of them I always have a delay.
setmintocopy does not change anything, as in your case. I also changed
the buffer size , that does not change the delay either, once it is
large enough.<br>
<br>
I am stack and really do not know what I can do. I talked to the
manufacturer of my card (Chesio), but they have no idea why that
happens either.<br>
<br>
Anton<br>
<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">Hi, <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The only thing that amazes me is Wireshark. Why
is wireshark able to capture with such accuracy even if it uses
winpcap. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Is it possible to achieve accuracy if i used
packet.h functions to receive and then pcap to send the packets. Anton
have you tried that?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">BR<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
> From: <a moz-do-not-send="true"
href="mailto:winpcap-users-request@winpcap.org">winpcap-users-request@winpcap.org</a><br>
> Subject: Winpcap-users Digest, Vol 72, Issue 8<br>
> To: <a moz-do-not-send="true"
href="mailto:winpcap-users@winpcap.org">winpcap-users@winpcap.org</a><br>
> Date: Wed, 16 Mar 2011 02:08:28 -0700<br>
> <br>
> Send Winpcap-users mailing list submissions to<br>
> <a moz-do-not-send="true" href="mailto:winpcap-users@winpcap.org">winpcap-users@winpcap.org</a><br>
> <br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a moz-do-not-send="true"
href="https://www.winpcap.org/mailman/listinfo/winpcap-users">https://www.winpcap.org/mailman/listinfo/winpcap-users</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a moz-do-not-send="true"
href="mailto:winpcap-users-request@winpcap.org">winpcap-users-request@winpcap.org</a><br>
> <br>
> You can reach the person managing the list at<br>
> <a moz-do-not-send="true"
href="mailto:winpcap-users-owner@winpcap.org">winpcap-users-owner@winpcap.org</a><br>
> <br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of Winpcap-users digest..."<br>
> <br>
> <br>
> Today's Topics:<br>
> <br>
> 1. Re: PPP capture (Gianluca Varenni)<br>
> 2. Re: Winpcap-users Digest, Vol 72, Issue 7 (Akif Usman)<br>
> <br>
> <br>
>
----------------------------------------------------------------------<br>
> <br>
> Message: 1<br>
> Date: Tue, 15 Mar 2011 13:59:25 -0700<br>
> From: Gianluca Varenni <a moz-do-not-send="true"
href="mailto:Gianluca.Varenni@riverbed.com"><Gianluca.Varenni@riverbed.com></a><br>
> To: Anton Tremsin <a moz-do-not-send="true"
href="mailto:ast@ssl.berkeley.edu"><ast@ssl.berkeley.edu></a>, <a
moz-do-not-send="true" href="mailto:winpcap-users@winpcap.org">"winpcap-users@winpcap.org"</a><br>
> <a moz-do-not-send="true" href="mailto:winpcap-users@winpcap.org"><winpcap-users@winpcap.org></a><br>
> Subject: Re: [Winpcap-users] PPP capture<br>
> Message-ID:<br>
> <a moz-do-not-send="true"
href="mailto:6A8F2E88CFF83C43A6AFF7FAC775B9FC07151743D9@MAILBOXES2.nbttech.com"><6A8F2E88CFF83C43A6AFF7FAC775B9FC07151743D9@MAILBOXES2.nbttech.com></a><br>
> Content-Type: text/plain; charset="us-ascii"<br>
> <br>
> Anton,<br>
> <br>
> If I remember well, you are capturing from Ethernet, Akif is
capturing from PPP. The code paths for the two types of devices are
completely different (Ethernet goes through the WinPcap kernel driver,
PPP gets captured through Netmon).<br>
> <br>
> Have a nice day<br>
> GV<br>
> <br>
> From: Anton Tremsin [<a moz-do-not-send="true"
href="mailto:ast@ssl.berkeley.edu">mailto:ast@ssl.berkeley.edu</a>]<br>
> Sent: Monday, March 14, 2011 11:43 PM<br>
> To: <a moz-do-not-send="true"
href="mailto:winpcap-users@winpcap.org">winpcap-users@winpcap.org</a><br>
> Cc: Gianluca Varenni<br>
> Subject: Re: [Winpcap-users] PPP capture<br>
> <br>
> Akif, Gianluca,<br>
> <br>
> As I mentioned in my previous messages, I have exactly the same
problem of delayed packages, with mintocopy set even to 0 (tried other
values as well). I am always sending a set of 64 packets of 8Kbytes
each (that is one image data). The packets are not lost, they always
arrive. However, some of them come with no delay (varied number of
them, sometimes 62, sometimes 57, etc), while the rest of them come
exactly after the delay equal to the setting of the timeout, which I
varied between 1 and 10000 milliseconds. There is no timeout reported
for the packets to arrive with the delay.<br>
> <br>
> I will be very glad if that issue can be solved, which has
probably the same cause as in Akif's application.<br>
> <br>
> Thanks a lot,<br>
> <br>
> Anton<br>
> <br>
> Akif,<br>
> <br>
> This is probably due to the mintocopy and timeout of WinPcap.
WinPcap does not deliver you the packets immediately after they are
received by the driver. Packets are batched in kernel mode and
delivered to the receiving application when<br>
> <br>
> <br>
> There are at least mintocopy bytes in the kernel buffer<br>
> <br>
> After a certain timeout<br>
> (whatever happens first).<br>
> <br>
> In order to reduce the delay, you will need to either reduce the
timeout or the mintocopy.<br>
> <br>
> Have a nice day<br>
> GV<br>
> <br>
> From: <a moz-do-not-send="true"
href="mailto:winpcap-users-bounces@winpcap.org">winpcap-users-bounces@winpcap.org</a><a
moz-do-not-send="true" href="mailto:winpcap-users-bounces@winpcap.org"><mailto:winpcap-users-bounces@winpcap.org></a>
[<a moz-do-not-send="true"
href="mailto:winpcap-users-bounces@winpcap.org">mailto:winpcap-users-bounces@winpcap.org</a>]
On Behalf Of Akif Usman<br>
> Sent: Thursday, March 10, 2011 11:20 AM<br>
> To: <a moz-do-not-send="true"
href="mailto:winpcap-users@winpcap.org">winpcap-users@winpcap.org</a><a
moz-do-not-send="true" href="mailto:winpcap-users@winpcap.org"><mailto:winpcap-users@winpcap.org></a><br>
> Subject: [Winpcap-users] PPP capture<br>
> <br>
> HI,<br>
> <br>
> I have installed the winpcap version 3.1 beta and i am capturing
from a PPP interface and it captures perfectly. Now i am trying to
capture from the same PPP interface using my LIBPCAP program and
forward it to another Ethernet interface that connects further to a
second computer (Ethernet NIC) which also has wireshark running on it.
When i capture from the second computer i get a strange offset of 0.5
seconds after every x packets. This is very strange. I dont know why
wireshark is able to capture from PPP interface on the first computer
with proper accuracy and why my LIBPCAP program, which is just
forwarding the packets, is introducing a 0.5s [:-O] delay. Please help
me out as soon as somebody can.<br>
> <br>
> Best Regards<br>
> Fika<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> <br>
> Winpcap-users mailing list<br>
> <br>
> <a moz-do-not-send="true" href="mailto:Winpcap-users@winpcap.org">Winpcap-users@winpcap.org</a><a
moz-do-not-send="true" href="mailto:Winpcap-users@winpcap.org"><mailto:Winpcap-users@winpcap.org></a><br>
> <br>
> <a moz-do-not-send="true"
href="https://www.winpcap.org/mailman/listinfo/winpcap-users">https://www.winpcap.org/mailman/listinfo/winpcap-users</a><br>
> <br>
> <br>
> <br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <a moz-do-not-send="true"
href="http://www.winpcap.org/pipermail/winpcap-users/attachments/20110315/7cb51127/attachment-0001.html"><http://www.winpcap.org/pipermail/winpcap-users/attachments/20110315/7cb51127/attachment-0001.html></a><br>
> <br>
> ------------------------------<br>
> <br>
> Message: 2<br>
> Date: Wed, 16 Mar 2011 10:08:25 +0100<br>
> From: Akif Usman <a moz-do-not-send="true"
href="mailto:akif.usman@hotmail.com"><akif.usman@hotmail.com></a><br>
> To: <a moz-do-not-send="true"
href="mailto:winpcap-users@winpcap.org"><winpcap-users@winpcap.org></a><br>
> Subject: Re: [Winpcap-users] Winpcap-users Digest, Vol 72, Issue 7<br>
> Message-ID: <a moz-do-not-send="true"
href="mailto:SNT143-w3812119493BFBBEDF1C2EC80CE0@phx.gbl"><SNT143-w3812119493BFBBEDF1C2EC80CE0@phx.gbl></a><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
> <br>
> <br>
> HI,<br>
> There are some questiosn i need to ask. Why does wireshark give no
delay upon capture even though it uses Winpcap? <br>
> I am using windows xp for capture and i have checked the capture
on ethernet and there seems to be no problems at all from the capture
on ethernet. I have tried changing mintocopy and the timeout but it
gives me no changes in the performance? Any ideas why?<br>
> <br>
> BR<br>
> <br>
> > From: <a moz-do-not-send="true"
href="mailto:winpcap-users-request@winpcap.org">winpcap-users-request@winpcap.org</a><br>
> > Subject: Winpcap-users Digest, Vol 72, Issue 7<br>
> > To: <a moz-do-not-send="true"
href="mailto:winpcap-users@winpcap.org">winpcap-users@winpcap.org</a><br>
> > Date: Tue, 15 Mar 2011 12:00:02 -0700<br>
> > <br>
> > Send Winpcap-users mailing list submissions to<br>
> > <a moz-do-not-send="true"
href="mailto:winpcap-users@winpcap.org">winpcap-users@winpcap.org</a><br>
> > <br>
> > To subscribe or unsubscribe via the World Wide Web, visit<br>
> > <a moz-do-not-send="true"
href="https://www.winpcap.org/mailman/listinfo/winpcap-users">https://www.winpcap.org/mailman/listinfo/winpcap-users</a><br>
> > or, via email, send a message with subject or body 'help' to<br>
> > <a moz-do-not-send="true"
href="mailto:winpcap-users-request@winpcap.org">winpcap-users-request@winpcap.org</a><br>
> > <br>
> > You can reach the person managing the list at<br>
> > <a moz-do-not-send="true"
href="mailto:winpcap-users-owner@winpcap.org">winpcap-users-owner@winpcap.org</a><br>
> > <br>
> > When replying, please edit your Subject line so it is more
specific<br>
> > than "Re: Contents of Winpcap-users digest..."<br>
> > <br>
> > <br>
> > Today's Topics:<br>
> > <br>
> > 1. Re: PPP capture (Gianluca Varenni)<br>
> > 2. Re: PPP capture (Anton Tremsin)<br>
> > <br>
> > <br>
> >
----------------------------------------------------------------------<br>
> > <br>
> > Message: 1<br>
> > Date: Mon, 14 Mar 2011 18:44:54 -0700<br>
> > From: Gianluca Varenni <a moz-do-not-send="true"
href="mailto:Gianluca.Varenni@riverbed.com"><Gianluca.Varenni@riverbed.com></a><br>
> > To: <a moz-do-not-send="true"
href="mailto:winpcap-users@winpcap.org">"winpcap-users@winpcap.org"</a>
<a moz-do-not-send="true" href="mailto:winpcap-users@winpcap.org"><winpcap-users@winpcap.org></a><br>
> > Subject: Re: [Winpcap-users] PPP capture<br>
> > Message-ID:<br>
> > <a moz-do-not-send="true"
href="mailto:6A8F2E88CFF83C43A6AFF7FAC775B9FC07151739AA@MAILBOXES2.nbttech.com"><6A8F2E88CFF83C43A6AFF7FAC775B9FC07151739AA@MAILBOXES2.nbttech.com></a><br>
> > Content-Type: text/plain; charset="us-ascii"<br>
> > <br>
> > Akif,<br>
> > <br>
> > This is probably due to the mintocopy and timeout of WinPcap.
WinPcap does not deliver you the packets immediately after they are
received by the driver. Packets are batched in kernel mode and
delivered to the receiving application when<br>
> > <br>
> > <br>
> > - There are at least mintocopy bytes in the kernel buffer<br>
> > <br>
> > - After a certain timeout<br>
> > (whatever happens first).<br>
> > <br>
> > In order to reduce the delay, you will need to either reduce
the timeout or the mintocopy.<br>
> > <br>
> > Have a nice day<br>
> > GV<br>
> > <br>
> > From: <a moz-do-not-send="true"
href="mailto:winpcap-users-bounces@winpcap.org">winpcap-users-bounces@winpcap.org</a>
[<a moz-do-not-send="true"
href="mailto:winpcap-users-bounces@winpcap.org">mailto:winpcap-users-bounces@winpcap.org</a>]
On Behalf Of Akif Usman<br>
> > Sent: Thursday, March 10, 2011 11:20 AM<br>
> > To: <a moz-do-not-send="true"
href="mailto:winpcap-users@winpcap.org">winpcap-users@winpcap.org</a><br>
> > Subject: [Winpcap-users] PPP capture<br>
> > <br>
> > HI,<br>
> > <br>
> > I have installed the winpcap version 3.1 beta and i am
capturing from a PPP interface and it captures perfectly. Now i am
trying to capture from the same PPP interface using my LIBPCAP program
and forward it to another Ethernet interface that connects further to a
second computer (Ethernet NIC) which also has wireshark running on it.
When i capture from the second computer i get a strange offset of 0.5
seconds after every x packets. This is very strange. I dont know why
wireshark is able to capture from PPP interface on the first computer
with proper accuracy and why my LIBPCAP program, which is just
forwarding the packets, is introducing a 0.5s [:-O] delay. Please help
me out as soon as somebody can.<br>
> > <br>
> > Best Regards<br>
> > Fika<br>
> > -------------- next part --------------<br>
> > An HTML attachment was scrubbed...<br>
> > URL: <a moz-do-not-send="true"
href="http://www.winpcap.org/pipermail/winpcap-users/attachments/20110314/fcd4e478/attachment-0001.html"><http://www.winpcap.org/pipermail/winpcap-users/attachments/20110314/fcd4e478/attachment-0001.html></a><br>
> > <br>
> > ------------------------------<br>
> > <br>
> > Message: 2<br>
> > Date: Mon, 14 Mar 2011 23:42:30 -0700<br>
> > From: Anton Tremsin <a moz-do-not-send="true"
href="mailto:ast@ssl.berkeley.edu"><ast@ssl.berkeley.edu></a><br>
> > To: <a moz-do-not-send="true"
href="mailto:winpcap-users@winpcap.org">winpcap-users@winpcap.org</a><br>
> > Cc: Gianluca Varenni <a moz-do-not-send="true"
href="mailto:Gianluca.Varenni@riverbed.com"><Gianluca.Varenni@riverbed.com></a><br>
> > Subject: Re: [Winpcap-users] PPP capture<br>
> > Message-ID: <a moz-do-not-send="true"
href="mailto:4D7F0A56.1070207@ssl.berkeley.edu"><4D7F0A56.1070207@ssl.berkeley.edu></a><br>
> > Content-Type: text/plain; charset="iso-8859-1";
Format="flowed"<br>
> > <br>
> > Akif, Gianluca,<br>
> > <br>
> > As I mentioned in my previous messages, I have exactly the
same problem <br>
> > of delayed packages, with mintocopy set even to 0 (tried
other values as <br>
> > well). I am always sending a set of 64 packets of 8Kbytes
each (that is <br>
> > one image data). The packets are not lost, they always
arrive. However, <br>
> > some of them come with no delay (varied number of them,
sometimes 62, <br>
> > sometimes 57, etc), while the rest of them come exactly after
the delay <br>
> > equal to the setting of the timeout, which I varied between 1
and 10000 <br>
> > milliseconds. There is no timeout reported for the packets to
arrive <br>
> > with the delay.<br>
> > <br>
> > I will be very glad if that issue can be solved, which has
probably the <br>
> > same cause as in Akif's application.<br>
> > <br>
> > Thanks a lot,<br>
> > <br>
> > Anton<br>
> > ><br>
> > > Akif,<br>
> > ><br>
> > > This is probably due to the mintocopy and timeout of
WinPcap. WinPcap <br>
> > > does not deliver you the packets immediately after they
are received <br>
> > > by the driver. Packets are batched in kernel mode and
delivered to the <br>
> > > receiving application when<br>
> > ><br>
> > > - There are at least mintocopy bytes in the kernel buffer<br>
> > ><br>
> > > - After a certain timeout<br>
> > ><br>
> > > (whatever happens first).<br>
> > ><br>
> > > In order to reduce the delay, you will need to either
reduce the <br>
> > > timeout or the mintocopy.<br>
> > ><br>
> > > Have a nice day<br>
> > ><br>
> > > GV<br>
> > ><br>
> > > *From:* <a moz-do-not-send="true"
href="mailto:winpcap-users-bounces@winpcap.org">winpcap-users-bounces@winpcap.org</a>
<br>
> > > [<a moz-do-not-send="true"
href="mailto:winpcap-users-bounces@winpcap.org">mailto:winpcap-users-bounces@winpcap.org</a>]
*On Behalf Of *Akif Usman<br>
> > > *Sent:* Thursday, March 10, 2011 11:20 AM<br>
> > > *To:* <a moz-do-not-send="true"
href="mailto:winpcap-users@winpcap.org">winpcap-users@winpcap.org</a><br>
> > > *Subject:* [Winpcap-users] PPP capture<br>
> > ><br>
> > > HI,<br>
> > ><br>
> > > I have installed the winpcap version 3.1 beta and i am
capturing from <br>
> > > a PPP interface and it captures perfectly. Now i am
trying to capture <br>
> > > from the same PPP interface using my LIBPCAP program and
forward it to <br>
> > > another Ethernet interface that connects further to a
second computer <br>
> > > (Ethernet NIC) which also has wireshark running on it.
When i capture <br>
> > > from the second computer i get a strange offset of 0.5
seconds after <br>
> > > every x packets. This is very strange. I dont know why
wireshark is <br>
> > > able to capture from PPP interface on the first computer
with proper <br>
> > > accuracy and why my LIBPCAP program, which is just
forwarding the <br>
> > > packets, is introducing a 0.5s [:-O] delay. Please help
me out as soon <br>
> > > as somebody can.<br>
> > ><br>
> > > Best Regards<br>
> > ><br>
> > > Fika<br>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > Winpcap-users mailing list<br>
> > > <a moz-do-not-send="true"
href="mailto:Winpcap-users@winpcap.org">Winpcap-users@winpcap.org</a><br>
> > > <a moz-do-not-send="true"
href="https://www.winpcap.org/mailman/listinfo/winpcap-users">https://www.winpcap.org/mailman/listinfo/winpcap-users</a><br>
> > > <br>
> > <br>
> > -------------- next part --------------<br>
> > An HTML attachment was scrubbed...<br>
> > URL: <a moz-do-not-send="true"
href="http://www.winpcap.org/pipermail/winpcap-users/attachments/20110314/fde1d594/attachment-0001.html"><http://www.winpcap.org/pipermail/winpcap-users/attachments/20110314/fde1d594/attachment-0001.html></a><br>
> > <br>
> > ------------------------------<br>
> > <br>
> > _______________________________________________<br>
> > Winpcap-users mailing list<br>
> > <a moz-do-not-send="true"
href="mailto:Winpcap-users@winpcap.org">Winpcap-users@winpcap.org</a><br>
> > <a moz-do-not-send="true"
href="https://www.winpcap.org/mailman/listinfo/winpcap-users">https://www.winpcap.org/mailman/listinfo/winpcap-users</a><br>
> > <br>
> > <br>
> > End of Winpcap-users Digest, Vol 72, Issue 7<br>
> > ********************************************<br>
> <br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <a moz-do-not-send="true"
href="http://www.winpcap.org/pipermail/winpcap-users/attachments/20110316/cd1b5258/attachment.html"><http://www.winpcap.org/pipermail/winpcap-users/attachments/20110316/cd1b5258/attachment.html></a><br>
> <br>
> ------------------------------<br>
> <br>
> _______________________________________________<br>
> Winpcap-users mailing list<br>
> <a moz-do-not-send="true" href="mailto:Winpcap-users@winpcap.org">Winpcap-users@winpcap.org</a><br>
> <a moz-do-not-send="true"
href="https://www.winpcap.org/mailman/listinfo/winpcap-users">https://www.winpcap.org/mailman/listinfo/winpcap-users</a><br>
> <br>
> <br>
> End of Winpcap-users Digest, Vol 72, Issue 8<br>
> ********************************************<o:p></o:p></p>
</div>
<pre> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Winpcap-users mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:Winpcap-users@winpcap.org">Winpcap-users@winpcap.org</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true"
href="https://www.winpcap.org/mailman/listinfo/winpcap-users">https://www.winpcap.org/mailman/listinfo/winpcap-users</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<p class="MsoNormal"><br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Anton S. Tremsin, Ph.D.<o:p></o:p></pre>
<pre>Space Sciences Laboratory<o:p></o:p></pre>
<pre>University of California at Berkeley<o:p></o:p></pre>
<pre>Berkeley, CA 94720<o:p></o:p></pre>
<pre>Tel: (510) 642 4554<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Winpcap-users mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:Winpcap-users@winpcap.org">Winpcap-users@winpcap.org</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true"
href="https://www.winpcap.org/mailman/listinfo/winpcap-users">https://www.winpcap.org/mailman/listinfo/winpcap-users</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<br>
</body>
</html>