- Re: IM drivers not returning packets to miniport ?
- Posted by Stephan Wolf on August 7th, 2003
Hi Larry,
I currently cannot think of any known issues that would cause this
particular behaviour. Have you run NDISTest against your Miniport? See
http://www.wd-3.com/071503/NDISTest.htm
Stephan
---
On Thu, 7 Aug 2003 09:41:08 -0500, "Larry Cawley"
<lcawley@earthlink.net> wrote:
- Posted by Larry Cawley on August 9th, 2003
Hi Stephen,
Looks like it is only the EAPOL packets from a WPA exchaange that are not
returned. Maybe this is unique to WPA.
We are running NdisTester. I'lll dig fruther into this....
Thanks,
larry.
"Stephan Wolf" <stewo68@hotmail.com> wrote in message
news:3f32a48f.33155755@news.t-online.de...
- Posted by Bryan S. Burgin [MSFT] on August 12th, 2003
Larry,
Since these are received packets you're passing up, run "netstat -s". It
might help indicate why the packets are dropped (if they are) -- i.e.,
failed checksum, reassembly errors, etc. They should still be returned
even if an error is encountered. Also check the packet's flags, especially
the low-order four bits that identify the protocol (see ndis.h and
ntddndis.h in the wnet environment).
Bryan S. Burgin
bburgin@microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.
- Posted by Alireza Dabagh [MS] on August 15th, 2003
Hi Larry, is this a serialized driver or deserialized? If serialized, could
it be the packets are returned back to you synchronously by setting the
packet status to success instead of calling your ReturnPacket handler?
-ali
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Larry Cawley" <lcawley@earthlink.net> wrote in message
news:u3QBqDpXDHA.2392@TK2MSFTNGP10.phx.gbl...
