Ethereal-users: Re: [Ethereal-users] Fw: Intel(R) PRO/Wireless 2100 3B Network Connection - Gene

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Guy Harris <gharris@xxxxxxxxx>
Date: Fri, 04 Feb 2005 01:23:50 -0800
Simone Chemelli wrote:
I noticed that nearly all Intel Wireless adapters, and for sure Centrino based, are not correctly handled by Ethereal/Winpcap and many users report them as not working. 

As Ronnie noted, this is either a WinPcap issue, a Windows issue, or a
driver issue - Ethereal just makes a standard "pcap_open_live()" call
with the promiscuous-mode flag set or not set, depending on whether
you've requested promiscuous mode in the capture dialog.


Thank you for contacting Intel(R) Technical Support.
Please note that the drivers for all Intel(R) wireless adapters allow for promiscuous mode enabling but it is not an option that the user can set. The call to set into promiscuous or sniffing mode must be made by the software that requires this mode - eg the sniffer, management monitor, or other application. The call is made and the Intel driver will respond by placing the adapter(s) into promiscuous mode as needed. 

WinPcap's driver, as far as I know, makes the right kernel-mode NDIS
call to request promiscuous mode.  I *presume* that's what they're
referring to as "the call to set into promiscuous or sniffing mode".
The WinPcap developers would probably have to discuss this with Intel support.