NDIS Packet handling

NTDEV
1

Hi

I am in a bit of a confusion. How can I pass a packet from a user mode
application directly to an NDIS intermediate driver without it going
through the protocol driver? Can it be done through the IOCTL or do I have
to use Winsock?

Thanks in advance

Arijit

2

If your application just wants to put a packet on the wire, send your IM
an IOCTL with the payload to an interface created via NdisMCreateDevice
and then package up a NDIS_PACKET/NDIS_BUFFER and do an NdisSend. But
you should keep the protocol-reserved field NULL so that you know that
the packet was allocated from within the IM. But it sounds like you
want to write your own protocol driver instead of an IM driver. Or
maybe a TDI driver. If the frame type is IP, then you’ll have to
identify and pluck off any reply packets. Can you explain more about
what you are trying to accomplish?

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no
rights.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Arijit
Bhattacharyya
Sent: Tuesday, August 24, 2004 12:55 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] NDIS Packet handling

Hi

I am in a bit of a confusion. How can I pass a packet from a user mode
application directly to an NDIS intermediate driver without it going
through the protocol driver? Can it be done through the IOCTL or do I
have
to use Winsock?

Thanks in advance

Arijit

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

The packet pool pointer in NDIS_PACKET can also be used to distinguish
“your” packets from the incoming packets.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

----- Original Message -----
From: “Bryan Burgin”
To: “Windows System Software Devs Interest List”
Cc:
Sent: Tuesday, August 24, 2004 12:23 PM
Subject: RE: [ntdev] NDIS Packet handling

> If your application just wants to put a packet on the wire, send your IM
> an IOCTL with the payload to an interface created via NdisMCreateDevice
> and then package up a NDIS_PACKET/NDIS_BUFFER and do an NdisSend. But
> you should keep the protocol-reserved field NULL so that you know that
> the packet was allocated from within the IM. But it sounds like you
> want to write your own protocol driver instead of an IM driver. Or
> maybe a TDI driver. If the frame type is IP, then you’ll have to
> identify and pluck off any reply packets. Can you explain more about
> what you are trying to accomplish?
>
> Bryan S. Burgin
> xxxxx@microsoft.com
>
> This posting is provided “AS IS” with no warranties, and confers no
> rights.
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Arijit
> Bhattacharyya
> Sent: Tuesday, August 24, 2004 12:55 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] NDIS Packet handling
>
> Hi
>
> I am in a bit of a confusion. How can I pass a packet from a user mode
> application directly to an NDIS intermediate driver without it going
> through the protocol driver? Can it be done through the IOCTL or do I
> have
> to use Winsock?
>
> Thanks in advance
>
> Arijit
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: unknown lmsubst tag argument:
> ‘’
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>