winxp ddk mux and passthru samples

NTDEV
1

Some time ago, I posted an issue installing the winxp ddk mux and
passthru samples concurrently. The problem is that the passthru never
binds into the stack because the mux’s notify object breaks all bindings
to the physical adapters that are not from the mux.

My question is whether you think the following workaround is ok. I
changed the LowerRange value in the mux’s miniport inf from “nolower” to
“ethernet”. Now the passthru binds above the mux. (The passthru also
tries to bind directly to the physical adapter but it is denied by the
mux’s notify object.) I ask this question because the xp ddk explictly
states:

ddk> The miniport inf file must define the upper edge bindings as
follows:
ddk> HKR, Ndi\Interfaces, UpperRange, 0, “ndis5”
ddk> HKR, Ndi\Interfaces, LowerRange, 0, “nolower”

I know I could have modified the mux’s notify object. However, I was
using the ddk sample code to understand the behavior of Compaq’s Network
Teaming software which is implemented as a 1-n mux. Not only do I not
have access to the source of the teaming software’s notify object,
teaming may just not like 3rd party drivers residing between their mux
and physical adapter drivers.

Thanks,
Dave

2

It may be a simple solution which is to rename the
Compaq notity DLL before install your passthru driver.
It would make your passthru sits right above the
physical NICs.

Cheers,
Minfeng Li

Some time ago, I posted an issue installing the winxp ddk mux and
passthru samples concurrently. The problem is that the passthru never
binds into the stack because the mux’s notify object breaks all bindings
to the physical adapters that are not from the mux.

My question is whether you think the following workaround is ok. I
changed the LowerRange value in the mux’s miniport inf from “nolower” to
“ethernet”. Now the passthru binds above the mux. (The passthru also
tries to bind directly to the physical adapter but it is denied by the
mux’s notify object.) I ask this question because the xp ddk explictly
states:

ddk> The miniport inf file must define the upper edge bindings as
follows:
ddk> HKR, Ndi\Interfaces, UpperRange, 0, “ndis5”
ddk> HKR, Ndi\Interfaces, LowerRange, 0, “nolower”

I know I could have modified the mux’s notify object. However, I was
using the ddk sample code to understand the behavior of Compaq’s Network
Teaming software which is implemented as a 1-n mux. Not only do I not
have access to the source of the teaming software’s notify object,
teaming may just not like 3rd party drivers residing between their mux
and physical adapter drivers.

Thanks,
Dave

You are currently subscribed to ntdev as: xxxxx@attbi.com
To unsubscribe send a blank email to %%email.unsub%%