Hello!
I have a question that is a bit offtopic here (although it is related), but I
don't know other places where I can ask it. But from mailing list archive I've
understood that some peoples that know the answer to my question are subscribed
to this list.
I'm writing a intermediate driver for NT that should intercept both TCP/IP and
NetBIOS data stream; the problem is that it works okay with Ethernet cards but
doesn't with NdisWAN pseudo-adapters. Two main questions:
a) TCP/IP seems to blatantly ignore the bindings set by NCPA for NdisWAN: even
if I disable the TCP/IP->NdisWAN# binding it anyway works; moreover, if I
disable the binding between TCP/IP and NdisWAN and try to force TCP/IP work
through my "virtual" driver by rising the priority of my driver (moving it up
in the binding tree), it anyway works through NdisWAN! How do I redirect TCP/IP
through my "driver" instead of NdisWAN? Do I have to mess with registry each
time driver loads (instead of using the .INF script)?
b) Which medium type should I indicate when "replacing" NdisWAN? If I indicate
NdisMediumWAN (as NdisWAN reports) NT traps somewhere in NDIS.SYS because it
first frees all packet filter records (EthDB, TrDB, FddiDB etc in my
NDIS_MINIPORT_BLOCK, then for some reason it tries to access the Ethernet
filter (by a NULL pointer) and traps). What additional functionality should I
provide? If I indicate NdisMediumEthernet instead of NdisMediumWan it anyway
traps in a different place, but also in NDIS.SYS.
Greetings,
_\ndy@teamOS/2
