Re: packet does not get to tcp ip
- From: "Maxim S. Shatskih" <maxim@xxxxxxxxxxxxxxxx>
- Date: Mon, 21 Aug 2006 23:15:29 +0400
1. Indicate each buffer to NDIS in its own packet containing only one
buffer - this seems to me inefficient
No. This will break the packet boundaries.
2. Copy all the buffers to a single buffer and indicate the new buffer
to ndis in a single packet - this seems to me even less efficient
Can be the only way.
3. Override the lookahead setting to be 0 so the first buffer will
contain only the ethernet header
No. TCP/IP requires the IP/TCP/UDP headers to also fit the first buffer.
Anyway - the lookahead size is the protocol's order to you, you cannot ignore
it.
--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@xxxxxxxxxxxxxxxx
http://www.storagecraft.com
.
- Follow-Ups:
- Re: packet does not get to tcp ip
- From: miki
- Re: packet does not get to tcp ip
- References:
- packet does not get to tcp ip
- From: miki
- Re: packet does not get to tcp ip
- From: miki
- packet does not get to tcp ip
- Prev by Date: Re: packet does not get to tcp ip
- Next by Date: Installing NDIS intermediate mode driver using Bindview application code
- Previous by thread: Re: packet does not get to tcp ip
- Next by thread: Re: packet does not get to tcp ip
- Index(es):