Hi everybody!
One last (I hope) question regarding the packet.sys sample:
I want it to be able to listen to BOTH Ethernet and modem traffic.
The problem is, that I have to specify the medium type before
NdisRegisterProtocol.
Any idea of how I can do so without holding 2 separate drivers?
In addition - when I replaced the 802_3 struct with an NdisWan medium,
the modem has stopped transferring packets all the time that the driver
was running… Why is that? (I took the original source, and replaced only
the medium).
thank you ever so much,
Barak Mandelovich xxxxx@mercury.co.il
Mercury Interactive ltd.
hi ,
You just can’t change the medium to NdisWanMedium the reason is that
the WAN medium drivers are NDIS WAN drivers and talk to NDIS WAN rather
than ndis.They are written in order to use PPP (point to point protocols)
and TAPI (telephonic API).The whole of the code would differ for both types
of drivers.So you cannot expect that your driver will work if you put NDIS
WAN MEDIUM.
Thanks
Ajitabh
-----Original Message-----
From: Barak Mandelovich [SMTP:xxxxx@mercury.co.il]
Sent: Wednesday, August 09, 2000 3:13 PM
To: NT Developers Interest List
Subject: [ntdev] packet.sys question
Hi everybody!
One last (I hope) question regarding the packet.sys sample:
I want it to be able to listen to BOTH Ethernet and modem traffic.
The problem is, that I have to specify the medium type before
NdisRegisterProtocol.
Any idea of how I can do so without holding 2 separate drivers?
In addition - when I replaced the 802_3 struct with an NdisWan medium,
the modem has stopped transferring packets all the time that the driver
was running… Why is that? (I took the original source, and replaced only
the medium).
thank you ever so much,
Barak Mandelovich xxxxx@mercury.co.il
Mercury Interactive ltd.
You are currently subscribed to ntdev as: xxxxx@future.futsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)