Just thought I’d post a follow up to my previous post in regards to an issue
I’m having with my driver (see below for background).
After a couple of days of research I’ve come up with the following:
* This bug does infact occur in an unmodified version of passthru (ntddk)
on windows 2000 with a netgear fa 311 nic card (blank install).
* There was a bug report for the exact problem that I’m describing
(http://www.pcausa.com/support/KB05280101.htm), but I was unable to get
their suggested methods to solve the problem working. Their point was that
the IM driver was not handling OID_TCP_TASK_OFFLOAD correctly and as such
was causing unpredictable results on certain adapters. My research lead me
to find that nothing was calling MiniportQueryInformation with said Oid at
anytime. Needless to say this left me perplexed and dismayed. I did note
that the report listed only NDIS5 as being affected but I figured it might
be worth a shot.
* It doesn’t appear to be any one specific packet that causes the adapter
to reset. This was verified by putting KdPrint’s inside ProtocolReceive()
and printing out the packets information.
* Finally, with lacking further direction, I’m going to attempt to put a
support call into microsoft to see if they might be able to provide any
further information lest someone on the list is able to provide insight.
Has anyone ever experienced similar problems with an unmodified version of
passthru for the ntddk (unpredictable results on certain ethernet adapters)?
Thanks,
Matt Miller
xxxxx@positivenetworks.net
====== previous post =======
Hi.
I was wondering if anyone might be able to shed some light on an extremely
elusive problem that I’m having in regards to machines with certain NIC
cards (linksys/netgear fa311) having their network functionality not work
correctly after a certain packet is sent.
Background:
My driver is an NDIS4 IM driver that does basic firewall packet filtering.
This functionality works flawlessly (as far as current testing is
considered). The driver itself is based off Microsoft’s passthru driver
that comes with the ntddk. Aside from adding a few key features such as wan
support, ioctl support, and of course, packet filtering, the driver itself
remains vastly untouched.
Problem: (occuring on win2k SP2 with a netgear fa 311 nic card)
In only one specific scenario have I seen and been able to recreate this.
After running an application in userland that uses nothing more than tcp to
communicate with another machine, the boxes network stops working. More
specifically: It can no longer send or receive packets. After starting
softice I’ve noted that for some reason the firewall driver’s ProtocolStatus
function is getting called two times in a row. The first time it gets
called with the general status being NDIS_STATUS_RESET_START and the second
time being NDIS_STATUS_RESET_END, respectively. This cycle happens multiple
times (once per packet almost is the pattern that I’ve been noticing,
although that may not actually be true) which would imply that the nic
driver is reseting over and over again. I’ve been unable to explain why the
nic driver would be reseting just because a TCP packet is being sent through
it (and that, after all, is probably not the root cause of this problem.)
I apogolize in advance if there isn’t a lot of information to go on here,
but to date it’s all that I’ve been able to dig up. I haven’t been able to
find the exact packet that causes the problem yet, and I’m hoping that if I
do it might shed more information, but I figured it optimal to ask for
opinions whilst I spent time doing that.
Thanks in advance.
Matt Miller
xxxxx@positivenetworks.net
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com