Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Home NTDEV
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


WSCInstallProvider() vs FwpmProviderAdd0()

CheckieViolaCheckieViola Member Posts: 2

I want to implement my own network provider to implement my protocols via WinAPI socket :
socket(MY_SOCKET_FAMILY, MY_SOCKET_TYPE, MY_SOCKET_PROTOCOL)
Previously WSCInstallProvider() function was used for this purpose, but now MSDN indicates that this is deprecated and not supported anymore, and you need to use FwpmProviderAdd0() function,however, I did not find any examples to implement your provider with the same functionality as WSCInstallProvider(), besides, I don't quite understand how Fwpmxxx () works.
Can someone tell me how I can achieve my goal? Thank!

Comments

  • MBond2MBond2 Member Posts: 277

    I gather that you have an existing Layered Service Provider (LSP) and want to migrate it to newer OS versions? At a high level, what does your LSP do?

    The guidance to move to windows filtering platform is very generic. Many and probably most LSPs were developed to filter connections or packets in some way and WFP is a much easier way to do that. But your description of a custom address family does not jive with that. Usually though, custom address family requires a NDIS protocol driver and not an LSP so I am confused

  • CheckieViolaCheckieViola Member Posts: 2

    my LSP doesn't intercept or filter anything, but just implements the windows sockets interface in user mode for my own transport, and I don't want to depend on the TCP/IP stack, which precludes the use of NDIS...

  • MBond2MBond2 Member Posts: 277

    If you don't do filtering, then a filtering platform is not what you need

    I don't think you understand how NDIS works if you think that the use of it in any way ties you to TCP/IP. It is specifically designed to be multi-protocol, but implementing an NDIS protocol driver is a very large task.

    I have not looked into this in some time, but I am not aware of a way to implement a network protocol in UM on modern Windows

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Writing WDF Drivers 7 Dec 2020 LIVE ONLINE
Internals & Software Drivers 25 Jan 2021 LIVE ONLINE
Developing Minifilters 8 March 2021 LIVE ONLINE