Yes, I agree. GetAdapterList call does not in any way interact with the NIC's miniport driver. It simply opens the Class GUID list of system adapters under HKLM\Sytstem\CurrentControlSet\Control\Class\[class]\xxxx and iterates through all class entries which have service name(in other words driver for the NIC has been installed).
As I replied in my previous E-mail, I also got "PAGE_FAULT_IN_NONPAGED_AREA" type of BOD, in npf.sys module. I do not belive this is an adpater driver issue since I can in fact sniff packets sent out the wireless link. The adapter I'm using is Cisco System 350 Series Wireless LAN Adapter. In my case the problem only manifested itself when several association/disassociations happened and the PacketSetNumWrites was set at 5000+. The same test went successful pretty consistently when the PacketSetNumWrites was set at 200, and the inter "burst" gap being about 150ms at the application level. -----Original Message----- From: Loris Degioanni [mailto:[EMAIL PROTECTED] Sent: Monday, July 14, 2003 7:04 AM To: [EMAIL PROTECTED] Subject: Re: [WinPcap-users] Problem with NPF driver on Wireless Adapter ? Hi, > Loris, > > Thank you for your reply. I already checked the registry of the > question > wireless adapter, but it is not corrupted. The application successfully > use > the question adapter to send/receive packets by winpcap, only sometimes > (rarely) it crash (bod) directly after I start the application. > > Is it possible that this problem occurred because of the wireless > adapter (driver) ? My WLAN adapter is "Intel PRO/Wireless 5000". Are > there any way to check this assumption ? I hardly believe this. getAdaptersList() doesn't interact in any way with the NIC driver or with NDIS. It simply perfroms registry queries. If you confirm that keyHandle is invalid, this can be only due to a problem in ZwOpenKey, which has nothing to do with the adapter model. Loris > Thank you again for your response, > Pun > > -----Original Message----- > From: Loris Degioanni [mailto:[EMAIL PROTECTED] > Sent: Monday, July 14, 2003 5:25 PM > To: [EMAIL PROTECTED] > Subject: Re: [WinPcap-users] Problem with NPF driver on Wireless Adapter > ? > > > The problem shouldn't have anything to do with the support of wireless > adapters. In every case, the driver shouldn't crash the system if an > adapter is not supported... > getAdaptersList() opens the registry, looks for some keys where the > adapter descriptions are normally stored, parses them and return the > result to the > DriverEntry() routine. Since keyHandle is initialized by ZwOpenKey, I > suppose that this routine is not able to properly open the registry key > of your wireless adapter, but for some reason it returns a successful > status. Did you check the presence and the correctness of the key in > question? Is it possible that the registry of the machine is somehow > corrupted? > > Loris > > > > > ================================================================== > This is the WinPcap users list. It is archived at > http://www.mail-archive.com/[EMAIL PROTECTED]/ > > To unsubscribe use > mailto: [EMAIL PROTECTED] > ================================================================== > > > > ================================================================== > This is the WinPcap users list. It is archived at > http://www.mail-archive.com/[EMAIL PROTECTED]/ > > To unsubscribe use > mailto: [EMAIL PROTECTED] > ================================================================== > ================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] ================================================================== ================================================================= This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] =================================================================
