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

Sept/Oct 2019 Issue of The NT Insider available


Download PDF here: http://insider.osr.com/2019/ntinsider_2019_01.pdf

It’s a particularly BIG issue, too: 40 pages of technical goodness, ranging from WDF to Minifilters. Check it out.
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

Protocol driver not receiving data even after the packet filters are set

sathish1323sathish1323 Member Posts: 7

I am running the Microsoft's intermediate driver sample code from window driver library. There are no modifications done to the sample. It is a latest library code downloaded from the github. There is a problem I am facing with the sample. After the installation of the intermediate driver, ndis is not calling the protocol driver's receive handler sometimes.
I see in the debug logs that the packet filters are set and the ndis request is always completing with success status. If it doesn't receive always, then there is some problem in setting the OID_CURRENT_PACKET_FILTER to the underlying miniport driver and I can find a way to fix it. But this sample sometimes it is receiving sometimes it is not.

If I do install/uninstall couple of times, protocol driver starts to receive the packets.

I am installing the intermediate driver in a hyper-v virtual machine. I hope the intermediate should behave the same for a virtual/physical machine.

This really bugging my head and this discussion from this would be a great help for me.

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
Writing WDF Drivers 21 Oct 2019 OSR Seminar Space & ONLINE
Internals & Software Drivers 18 Nov 2019 Dulles, VA
Kernel Debugging 30 Mar 2020 OSR Seminar Space
Developing Minifilters 27 Apr 2020 OSR Seminar Space & ONLINE