ndis passthru basic question



Hi all,

I'll like to ask some simple questions regarding the workings of the
ndis passthru.
Coming from a non-c and non-networking background i have some
difficulty understanding some parts of the code.

"This driver exposes a virtual adapter for each binding to a real or
virtual NDIS adapter."
For a system with 2 network cards does it mean that there will be 2
virtual adapters running concurrently?

"NDIS calls Passthru’s BindAdapterHandler and PtBindAdapter for each
underlying NDIS adapter to which it is configured to bind."

pAdapt is initialized in PtBindAdapter so what I'm confused about is
whether will there be 2 virtual adapter structures initialized in a
system with 2 adapters? If that is the case how does the code handle 2
different virtual adapters because I can only see one pAdapt, or does
it actually become 2 different drivers?

I've installed the "extended passthru 1" on a virtual machine which
only shows one hardware nic, and on running ptuserio.exe it shows 3
bindings in the console.(2 ndiswan and 1 vmware amd accelerated pcnet
adapter). It's explained in the site documentation that what shows on
the console corresponds to the miniports on the system but I don't
quite understand

Lastly, I'll like to ask, in the original passthru code, is there any
significance of adding referencing and dereferencing to the virtual
adapter if there is only one nic to bind to.

Thank you,
Joey
.



Relevant Pages

  • Re: ndis passthru basic question
    ... For Passthru there will be a virtual adapter "running" for each adapter that Passthru is bound to. ... On a system with one hardware NIC there may be other software-only NICs and there may be virtual NICs created by other components. ...
    (microsoft.public.development.device.drivers)
  • Re: selectively bind a NDIS IM
    ... If is is a specific adapter identified by hardware ID, the you can write a NDIS "Notify Object" that is run at install time. ... A Notify Object can restrict bindings to a specific VID/PID. ...
    (microsoft.public.development.device.drivers)
  • Re: NDIS-cable status
    ... for the adapter shows a "red X" and Network Connections shows "Network Cable ... my driver will redirect any traffic to the other adapter transparent to the ... > the NIC directly using a mechanism that bypasses the NDIS IM filter. ... >> but still the status of network connection becomes cable unpulgeed. ...
    (microsoft.public.development.device.drivers)
  • Re: How to change the IP address under the wince?
    ... you should be able to change the registry and then tell NDIS to rebind ... the adapter to be disconnected, ... > For restart you have two options. ...
    (microsoft.public.windowsce.app.development)
  • Passthru NDIS IM example on WinCE5.00 (WM5.0 PPC)
    ... I've got the Passthru example from the Platform Builder for WinCE500 ... The problem is that the Passthru driver seems to lock up if WiFi is ... it dies in ProtocolBindAdapter at the call to ... The adapter will bind properly and function as expected if the WiFi ...
    (microsoft.public.development.device.drivers)