On Mon, Jun 21, 2004 at 05:28:15PM +0300, Khanukov, Oleg wrote:
> Ethereal ... Windows ... and wireless support
...
> empty Interface field.
http://www.ethereal.com/faq.html#q5.5
although, as you're trying to use Ethereal on Windows to capture on an
802.11 interface, even if you manage to fix whatever probable-WinPcap
problem is causing no interfaces to be availabe, you may still not be
able to do anything useful - promiscuous mode might not work, so all you
might be able to do is to capture (in non-promiscuous mode) traffic
going to or from the machine on which you're running Ethereal.
People who want to capture, on Windows, general 802.11 traffic (rather
than just traffic to and from the machine running Ethereal) should
probably either
1) use Sniffer Wireless or AiroPeek for Windows
or
2) install Linux or FreeBSD (or NetBSD 2.0-beta) on their
machine
as you're probably not going to have much success with Ethereal on
Windows, due to limitations of Windows and the 802.11 drivers:
http://www.ndis.com/faq/QA01190301.htm
http://www.ndis.com/faq/QA08010302.htm
Perhaps Windows Longhorn will support "native 802.11", in which case
perhaps some future version of WinPcap will, on Windows Longhorn, allow
applications to capture on 802.11 devices in useful ways. I wouldn't
expect it to be useful before that, however, so I wouldn't expect
Ethereal - or Analyzer, or WinPcap, or ... - to be useful network
analyzers on 802.11 interfaces unless you're trying to analyze traffic
being sent by or to the machine running tha network analyzer.