RE: Problem with NDIS transport driver

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Bryan S. Burgin [MSFT] (bburgin_at_online.microsoft.com)
Date: 08/19/04 

Date: Thu, 19 Aug 2004 12:31:55 GMT

Marcin,

Probably not. Filter IM drivers (a.k.a. PASSTHRU), where there's a 1:1
relationship between protocols and miniports, will generally pass through
status indications even if it doesn't know what the status is (i.e., your
custom status codes). Bridging drivers, because they are sitting over two
miniports, can really only pass up status codes that it understands, and
therefore, yours will be blocked.

You should probably make a private interface between your transport and
miniport.

Bryan S. Burgin
bburgin@online.microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.

Relevant Pages

  • Re: network interface name
    ... > to NDIS 6 miniports at initialization time. ... NDIS drivers can only open and access registry entries: ...
    (microsoft.public.development.device.drivers)
  • Re: network driver and restart
    ... > NDIS IM drivers can't actually layer directly over the lower-level WAM ... > miniports. ... Not needed anyway, these packets are often encrypted, and the password never ...
    (microsoft.public.development.device.drivers)
  • Re: porting drivers
    ... drivers (since other things are not miniports). ... This can also be NIC drivers. ... Maxim Shatskih, Windows DDK MVP ...
    (microsoft.public.development.device.drivers)