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/
As far as I can figure out NET_BUFFER will always give me the entire packet including the layer 2 headers (ethernet , wifi , etc ...). Is there some robust way to get where the IP header starts inside the NET_BUFFER and not rely on parsing the frames based on NDIS_MEDIUM (or maybe even that is not a feasible way)?
Also, can I make any assumptions about NET_BUFFERs that are within the same list or same chain of lists like, for example them being of the same protocol ?
I mean I know I can get NdisGetNetBufferListProtocolId and it will say that a list is all TCP, but it does not say weather it's all IPv4 or all IPv6, also does not say anything about the other lists in the chain.
|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!||Kernel Debugging||30 Mar 2020||OSR Seminar Space|
|Developing Minifilters||15 Jun 2020||LIVE ONLINE|
|Writing WDF Drivers||22 June 2020||LIVE ONLINE|
|Internals & Software Drivers||28 Sept 2020||Dulles, VA|