Hello
I have NDIS6 LWF firewall driver. Currently it binds only to ethernet (FilterMediaTypes = ethernet). Everything ok for LAN and Wi-Fi. But I also need to support usb 3g modems. I did some testing and it looks like I need to bind to WAN miniports.
Is there some generic way to retrieve type of packet for specific miniport ?
For example there is miniport with BaseMiniportInstanceName "WAN Miniport (IP)”. I guess packets on such interface start with ip4 header. Ip6 for "WAN Miniport (IPv6)”. But what about miniport "WAN Miniport (Network Monitor)” ?
Look at NDIS_FILTER_ATTACH_PARAMETERS::MediaType.
BTW, it’s not enough to bind to the “NDIS WAN” miniport. You also will want to bind to the wmbclass miniport. Basically, there’s the old pre-Win7 way of building MBB adapters that uses the WAN stack, and the Win7+ way that goes through wmbclass. If you’re building a generic filter driver that needs to work in a variety of consumer configurations, you should get ahold of both types of MBB and test with both.
Thank you Jeffrey !
I’ll read in-depth about Windows cellular architecture now.
Unfortunately all WAN miniports report MiniportMediaType = NdisMediumWan and MiniportPhysicalMediaType = NdisPhysicalMediumUnspecified in NDIS_FILTER_ATTACH_PARAMETERS.
The only thing that gives some idea about base packet header is BaseMiniportInstanceName = “WAN Miniport (IP)” and BaseMiniportName = “\DEVICE\NDISWANIP”.
Maybe there is some other way to get information about packet structure on specific WAN miniport ?
Well that’s one of the problems of the pre-Win7 model… you can’t really know for sure that it’s WWAN, versus some other type of WAN. Prior to Windows 7, the OS didn’t really know about MBB, so NICs came up generically.
From: xxxxx@lists.osr.com on behalf of xxxxx@gmail.com
Sent: Wednesday, June 7, 2017 10:27:04 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] WAN adapter base network header type
Thank you Jeffrey !
I’ll read in-depth about Windows cellular architecture now.
Unfortunately all WAN miniports report MiniportMediaType = NdisMediumWan and MiniportPhysicalMediaType = NdisPhysicalMediumUnspecified in NDIS_FILTER_ATTACH_PARAMETERS.
The only thing that gives some idea about base packet header is BaseMiniportInstanceName = “WAN Miniport (IP)” and BaseMiniportName = “\DEVICE\NDISWANIP”.
Maybe there is some other way to get information about packet structure on specific WAN miniport ?
—
NTDEV is sponsored by OSR
Visit the list online at: https:
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:
To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:>
Thank you again Jeffrey !
So I guess no other way but rely on wan miniport name