Re: Windows Not Respond after calling NDISMIndicateReceivePacket

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Alireza Dabagh [MS] (alid_at_online.microsoft.com)
Date: 03/06/04 

Date: Sat, 6 Mar 2004 01:19:13 -0800

Assuming you construct a MAC header for the packet as you should (see the
response from Thomas), what do you set the destination mac address to? Make
sure it is not a multicast address.

-ali 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"Billy Ng" <anonymous@discussions.microsoft.com> wrote in message
news:0D643380-FFD9-4137-AE6D-4DC8F1A838B1@microsoft.com...
> I am developing a virtual network miniport driver which transfers packets
from the upper protocol driver and a user mode application via
DeviceIoControl calls.  I have problem to send packets back up to upper
protocol driver.  In testing, I expect windows to respond to the incoming
packets after NDISMIndicateReceivePacket is called.  For example, when the
incoming packet is ARP request, I would expect windows to send out ARP
reply.  Nothing happens.  The same thing happens when I tired to send back a
PING packet.
> In WinDbg, I looked at the Private member of the Packet structure.  It
show the correct MDL head and tail pointer (they are the same because the
ARP packet is 32 bytes).
>
> 1) Am I doing the right thing by calling NDISMIndicateReceivePacket to
indicate the incoming packet?  I have heard about another call,
NDISMETHIndicateReceive.  Should I use that instead?
> 2) Any flag or counter I need to worry about in the packet structure?
>
> Thanks in advance,
> Billy Ng.

Relevant Pages

  • RE: Transfer a sending packet to upper TCP/IP protocol layer in IM
    ... The original MAC header is INVALID because my IM driver will assign a new ... After prepending IPv4 header and UDP header to the original IPv6 packet, ...
    (microsoft.public.development.device.drivers)
  • Re: what is NDIS packet type
    ... NDIS does not know anything about packet types. ... Check the "type code / length" field in the MAC header. ...
    (microsoft.public.development.device.drivers)
  • Re: NDIS driver problem NdisMIndicateRecPkt (ARP doesnt get a respons
    ... Did you verify the OOB data? ... did you call NDIS_SET_PACKET_HEADER_SIZEwith the size of the MAC header? ... You indicated that the entire packet is described by one NDIS_BUFFER and so you should not have any issue with look-a-head minimums or headers crossing an NDIS_BUFFER edge. ... stack does call back to to my MPReturnPacket function ...
    (microsoft.public.development.device.drivers)
  • Re: NDIS Intermediate Driver - Adding new header
    ... Updating NDIS packet data without any change in the length of the packet. ... If you are modifying a packet that is being received it is easy to overlook ... If the total packet size including the MAC header is less than the lookahead ...
    (microsoft.public.development.device.drivers)
  • Re: NDIS - sending packets
    ... > allocated from a send packet pool on the adapter you are sending on. ... So one is free to use one and the same packet pool to allocate ... allocate your own MAC header ...
    (microsoft.public.development.device.drivers)