Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. A protocol driver may receive packets from NDIS even though the driver has its packet filters set to zero to disable packet reception

A protocol driver may receive packets from NDIS even though the driver has its packet filters set to zero to disable packet reception

View products that this article applies to.

Symptom

NDIS is indicating received data to any protocol drivers bound to a wireless miniport device even though the packet filter of a protocol driver is set to 0, i.e. disable packet reception by the protocol driver. Problem can be reproduced with the WDK NDIS protocol sample (ndisprot).  

↑ Back to the top

Cause

Before NDIS indicates a packet to the protocol driver, NDIS will do the check for a zero packet filter (which is the default for protocol driver) only if the media type is 802.3 or 802.5 (Ethernet or Token ring). For other media types (such as native wifi), NDIS won’t do the check for the protocol packet filter value and will indicate packets (that were indicated from the underlying miniport) unconditionally to the protocol driver.

↑ Back to the top

Resolution

The protocol driver needs to handle this situation by expecting that NDIS may call its ProtocolReceiveNetBufferLists function when indicating packets received from the miniport even though the protocol driver packet filter was set to zero.  

↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info
Article ID : 2661019
Revision : 1
Created on : 1/7/2017
Published on : 1/9/2012
Exists online : False
Views : 204