![]() For example, a WFP callout cannot interact with media-connect state, hardware offloads, or power management. WFP callouts operate at a different layer, and so have rather different strengths and weaknesses than an NDIS protocol or LWF. There are a few small corner cases, but generally you'll find that LWFs are powerful. Comparing LWFs, NDIS protocols, and WFP calloutsĪ LWF can do almost anything that an NDIS protocol driver can do. (Assuming NDIS 6.x for the miniport & protocol). These are all supported and current technologies. We are happy to see people write new LWFs, WFP callouts, NDIS miniports, or NDIS protocols. However, a low-level packet capturing toolkit is a perfect example of what LWFs are good for. Most people really want to work at layer-3 or layer-4, where they are better served by WFP than by a LWF. We don't talk about them much, simply because there is limited interest in them. LWFs are still quite supported by Microsoft. I hope you can convince upstream to take your changes :-) Regarding LWFs ![]() Congratulations on porting WinPcap to NDIS 6.x. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
May 2023
Categories |