ndis 5.0 intermediate driver

hi all,

i'm working on ndis 5.0 intermediate driver. Please tell me is there any way
to originate the packets from intermediate driver,not from the upper protocol
driver.If it is there, what is process to allocate packets and send it lower
drivers?

thanQ all.

Allocate NDIS_PACKET _from your own pool_, allocate NDIS_BUFFER to describe
the packet memory, chain it to the packet, fill the packet OOB fields
(forgotten the exact list, they are filled by macros like NDIS_SET_xxx) and
call NdisSend.

The issue is to distinguish this packet from the "upper" packets in
ProtocolSendComplete. Use the PacketPoolHandle field for this - if this is your
pool, then this is your packet, otherwise, it is the packet arrived from up.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation

http://www.storagecraft.com

"brahma" <> wrote in message
news:61B91640-0170-44A2-8115-...
> hi all,
>
> i'm working on ndis 5.0 intermediate driver. Please tell me is there any way
> to originate the packets from intermediate driver,not from the upper protocol
> driver.If it is there, what is process to allocate packets and send it lower
> drivers?
>
> thanQ all.

hi Maxim S. Shatskih,

Thanks for ur reply... Could you please tell me something about OOB data...?
is it required...? And for what it will be used..?

thaQ again...

"Maxim S. Shatskih" wrote:

> Allocate NDIS_PACKET _from your own pool_, allocate NDIS_BUFFER to describe
> the packet memory, chain it to the packet, fill the packet OOB fields
> (forgotten the exact list, they are filled by macros like NDIS_SET_xxx) and
> call NdisSend.
>
> The issue is to distinguish this packet from the "upper" packets in
> ProtocolSendComplete. Use the PacketPoolHandle field for this - if this is your
> pool, then this is your packet, otherwise, it is the packet arrived from up.
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
>
> http://www.storagecraft.com
>
> "brahma" <> wrote in message
> news:61B91640-0170-44A2-8115-...
> > hi all,
> >
> > i'm working on ndis 5.0 intermediate driver. Please tell me is there any way
> > to originate the packets from intermediate driver,not from the upper protocol
> > driver.If it is there, what is process to allocate packets and send it lower
> > drivers?
> >
> > thanQ all.
>
>

On May 30, 12:11 pm, brahma <bra...@discussions.microsoft.com> wrote:
> hi Maxim S. Shatskih,
>
> Thanks for ur reply... Could you please tell me something about OOB data...?
> is it required...? And for what it will be used..?

Excerpt from the DDK docs:

"The NDIS_PACKET_OOB_DATA structure specifies out-of-band information
associated with a packet descriptor, used by drivers whose media
supplies, requires, or accepts out-of-band information, such as
information for an ATM NIC, and by drivers that support multipacket
receives and/or sends."

The following oob info is currently defined:

TimeToSend
TimeSent
TimeReceived
HeaderSize
SizeMediaSpecificInfo
MediaSpecificInformation
Status

Most of them are optional ('Status' and 'HeaderSize' are mandatory).
See the description on NDIS_PACKET_OOB_DATA for details.

Stephan

thanQ Stephan Wolf.


"Stephan Wolf [MVP]" wrote:

> On May 30, 12:11 pm, brahma <bra...@discussions.microsoft.com> wrote:
> > hi Maxim S. Shatskih,
> >
> > Thanks for ur reply... Could you please tell me something about OOB data...?
> > is it required...? And for what it will be used..?
>
> Excerpt from the DDK docs:
>
> "The NDIS_PACKET_OOB_DATA structure specifies out-of-band information
> associated with a packet descriptor, used by drivers whose media
> supplies, requires, or accepts out-of-band information, such as
> information for an ATM NIC, and by drivers that support multipacket
> receives and/or sends."
>
> The following oob info is currently defined:
>
> TimeToSend
> TimeSent
> TimeReceived
> HeaderSize
> SizeMediaSpecificInfo
> MediaSpecificInformation
> Status
>
> Most of them are optional ('Status' and 'HeaderSize' are mandatory).
> See the description on NDIS_PACKET_OOB_DATA for details.
>
> Stephan
>
>