Hi All,

I have the following scenario: A virtual Miniport driver that indicate
a receive packet whenever a send command is issued, in order to receive
a send packet by the stack. A protocol driver binds to this Miniport
driver to send and receive packets from a user-mode application (via
IOCTRL). This work if a packet is read from the Miniport driver by the
protocol driver that is receive by the stack via a real network
adapter. But if a write packet is issued from the user-mode application
a send packet is commanded to the Miniport the packet is looped-back
and indicated as a received packet, then the stack receives the packet
as well as the protocol driver. This is because the protocol driver is
bind to the Miniport and receives all packets from the Miniport.

So how can I change this to not receive my own send packets but still
receive those coming from the stack?

Thanks.

"Amos" <hvz@telkomsa.net> wrote in message
news:1123228507.834099.30180@o13g2000cwo.googlegro ups.com...
initiate your sends. Just modify the virtual miniport to have an API to
user-mode. This API should be very similar to the API that you already have
to your protocol driver.

Now, with the protocol driver eliminated you have 1.) one less driver to
worry about and 2.) your problem of identifying which packet is yours has
gone away.

Good luck,

Thomas F. Divine, Windows DDK MVP
http://www.pcausa.com

Sorry, but this is kind of confusing me.

What exactly do you mean by "protocol" vs. "stack"?

Stephan
---
Amos wrote:

Thanks Thomas, but how will this solve my problem? If a packet is send
from the user-mode to the Miniport driver it still has to copy the
packet from the TCB (Transmit Control Buffer) to the RCB and indicate a
receive packet in order for the packet to reach the TCP\IP stack. If a
read packet is performed during this time, from the user-mode, will the
same packet be read or not? If not why?

Thank you.

"Amos" <hvz@telkomsa.net> wrote in message
news:1123487957.227487.194030@g43g2000cwa.googlegr oups.com...
I am afraid that Stephan got it right: We really don't understand what
you're trying to do and how you're trying to do it...

Thomas F. Divine