ndis 筛选驱动程序属于 NT 驱动程序还是 WDM 驱动程序？
NT驱动不支持插件和播放。
ndis过滤器属于NT驱动程序还是WDM驱动程序？
NT driver doesn't support plugin and play.
Does ndis filter belong to NT driver or WDM driver?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
NDIS 筛选器驱动程序通常是“传统 WDM”驱动程序。它们可以通过SCM（例如StartService API）启动/停止。
然而，NDIS 在技术上允许任何驱动程序成为 NDIS 筛选器驱动程序：只要驱动程序使用有效的 UniqueName 调用 NdisFRegisterFilterDriver，它就是一个筛选器。
NDIS 过滤器驱动程序不参与传统的WDM PNP 操作（例如，它们不处理IRP）。但是，NDIS 有自己的 PNP 模型，该模型允许动态创建、启动、停止和分离过滤器实例。 （事实上，如果过滤器在其 INF 文件中被标记为可选，则可以在不中断活动 TCP 连接的情况下插入和删除它。您甚至可以在不中断后台下载的情况下安装过滤器驱动程序！
）错误的想法——NDIS 过滤器模型确实非常现代、强大且灵活。它只是不使用 WDM 进行 PNP。
NDIS filter drivers are typically "legacy WDM" drivers. They can be started/stopped through SCM (e.g., the StartService API).
However, NDIS will technically permit any driver to be an NDIS filter driver: as long as the driver calls NdisFRegisterFilterDriver with a valid UniqueName, it's a filter.
NDIS filter drivers do not participate in traditional WDM PNP operations (e.g., they do not handle IRPs). However, NDIS has its own PNP model, which allows filters instances to be created, started, stopped, and detached dynamically. (In fact, if the filter is marked as Optional in its INF file, it can be inserted and removed without breaking active TCP connections. You can install a filter driver without even interrupting a background download!)
Don't walk away from this explanation with the wrong idea -- the NDIS filter model is really quite modern, powerful, and flexible. It just doesn't use WDM for PNP.