Hello,<br> <br> I am using the winpcap 4.0 library to send and receive <br> TCP/IP packets to/from a demo application running on a <br> Windows 2000/XP computer.<br> <br> From an earlier post, I learnt that setting the <br> 'read_timeout' parameter of pcap_open () to -1 causes <br> pcap_next_ex () to exhibit non-blocking behavior.<br> <br> In such a (non-blocking) configuration, what are the <br> parameters that determine when packets are copied out from <br> the kernel buffers into the user buffers (where they can be <br> retrieved via the pcap_next_ex () call)? Is the <br> pcap_setmintocopy () call still relevant in such a (non-<br> blocking) configuration? What role does the <br> PCAP_OPENFLAG_MAX_RESPONSIVENESS flag (specified in the <br> 'flags' parameter in the call to pcap_open ()) play?<br> <br> Also, one of the papers at this site talks about an API<br> call to set the size of the user
buffer. However, I<br> wasn't able to find any such function in the WinPcap<br> documentation. Can you please point me to the relevant<br> function?<br> <br> Thanks,<br> <br> Samir<p> 
<hr size=1>8:00? 8:25? 8:40? <a href="
http://tools.search.yahoo.com/shortcuts/?fr=oni_on_mail&#news"> Find a flick</a> in no time<br> with the<a href="
http://tools.search.yahoo.com/shortcuts/?fr=oni_on_mail&#news">Yahoo! Search movie showtime shortcut.</a>