Hi,

What happens if two protocol drivers set their own multicast address
list with OID_802_3_MULTICAST_LIST? Is it Miniport's responsibility to
OR those two list, create a global list and send to the adapter or
NDIS will take care of creating a global list of multicast address and
send to Miniport via OID_802_3_MULTICAST_LIST?

Also who will route the RX frames filtered via global multicast
address list to the respective protocol drivers?

Thanks,
Aniketa

NDIS does this.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

NDIS keeps one multicast list per protocol and passes a combined list
to the miniport.

NDIS also filters received frames per protocol (unless a protocol has
set the NDIS_PACKET_TYPE_ALL_MULTICAST packet filter bit).

Stephan
---
On Jan 25, 6:40*am, Aniketa K S <aniket...@rediffmail.com> wrote:

On Jan 25, 2:39 pm, "Stephan Wolf [MVP]" <stew...@hotmail.com> wrote:
Thanks Maxim and Stephan.

One more question. So if one of the protocol driver has set/unset the
NDIS_PACKET_TYPE_ALL_MULTICAST global flag, then all the other bound
protocol drivers have to accept this and go on? Or again will NDIS
manage this internally and issues the OID_802_3_MULTICAST_LIST (or
OID_GEN_CURRENT_PACKET_FILTER with NDIS_PACKET_TYPE_ALL_MULTICAST flag
set/unset) only if all the bounded protocol drivers set/unset this
flag?

Thanks,
Aniketa

Yes.

Each protocol only receives the packets which it asked for.

To employ the possible hardware filters, NDIS maintains the logical OR of all
filters by all protocols and sets it to the miniport.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com