[Winpcap-users] Risk related to using winPcap in place of

[Gianluca Varenni]

WinPcap does not bypass the OS. It bypasses the TCP/IP stack. WinPcap is a protocol driver and sits in parallel with the TCP/IP protocol driver. It communicates with the NICs through their drivers using NDIS (which is the standard networking infrastructure on Windows). Figure 2 of the ISCC paper.

Have a nice day
GV



From: Bilal Shahid 
Sent: Friday, July 09, 2010 6:26 AM
To: winpcap-users at winpcap.org 
Subject: [Winpcap-users] Risk related to using winPcap in place of


> Do you have any reason to believe that if you implement your own protocol (or re-implement existing protocols) you will actually reduce latency?It bypasses OS and transport and application layer by going directly to wire is the reason why I think it will reduce latency. 

These two articles on wincap.org also imply the same

http://www.winpcap.org/docs/WinPcap-SBAC03.pdf

http://www.winpcap.org/docs/iscc01-wpcap.pdf



--------------------------------------------------------------------------------


_______________________________________________
Winpcap-users mailing list
Winpcap-users at winpcap.org
https://www.winpcap.org/mailman/listinfo/winpcap-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winpcap.org/pipermail/winpcap-users/attachments/20100709/42e84bd1/attachment.htm