Re: NDIS miniport Driver - packet re-ordering



I agree with GV that you don't need to reorder the packet.
But the question is why your packets not ordering? Is sender issue or
receiver issue?
You might fail on WDK NDIS testing if your packets are not ordering.

"Gianluca Varenni" <gianluca.varenni@xxxxxxxxxxxxxxxx>
The IP protocol driver is responsible for reordering the packets. A
miniport driver is just responsible for delivering packets to the upper
layers as they are received, discarding packets with L2/physical errors
(e.g. wrong FCS).

Hope it helps
GV

--
Gianluca Varenni, Windows DDK MVP

CACE Technologies
http://www.cacetech.com


"James Jin" <dosincerity@xxxxxxxxx> wrote in message
news:ff32d982-5cff-4985-acb2-061cb4356e6e@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,

I'm developing ndis-usb miniport driver.
If IP packet order was corrupted by any reason, Have to I re-order IP
packet?


I've reviewed the TCP / IP Layer concepts in wikipedia.org.
The doc said that TCP layer re-ordered Packets.


NDIS miniport driver isn't TCP / IP layer, so don't have to re-order
packet. right?


Best regards.




.



Relevant Pages

  • Re: Simulating smaller MTU? ie sending small packets.
    ... This is due to the fact that TCP ... If you want smaller packets, ... >> set there as the MSS is announced by the receiver during the ... Yes, per connection. ...
    (comp.lang.perl.misc)
  • Re: Simulating smaller MTU? ie sending small packets.
    ... The smaller the packets are, ... This is due to the fact that TCP ... > What I observe is that once the receiver is not ... > keeping up with the speed the sender is spewing packets, ...
    (comp.lang.perl.misc)
  • Re: .Net TCP Socket Problem With Missing Chunks From Large Packets
    ... >> An acquaintance asked me to assist him with some TCP socket issues. ... However, when large packets are sent over longer>> distances, the data arrives with portions missing. ... That means that if you send n bytes, the> receiver might receive anywhere from 1 to n bytes when reading data out of> the socket. ...
    (microsoft.public.dotnet.framework.remoting)
  • RE: Timeout strategy: terminal vs Telnet drivers
    ... >>> layer may or may not send them as individual packets. ... > The context was Telnet which IS an application wrt TCP ...
    (comp.os.vms)
  • Re: Need a script to understand names posts
    ... the physical layer of the ISO model, augmented by providing all of the logic ... a network model that does more than just detect the fact that packets ... and brings them back onto the network as if they had never been lost. ... the packets previously lost will never ever be lost again, ...
    (microsoft.public.scripting.wsh)