Question : sniffing with ethereal and Linksys Wireless-G PCI Adapter

I am running Windows XP.  I have a wireless Linksys WRT54G router on a SBC DSL line.  I use a wired connection from the base computer to the router.  The base computer also has a Linksys Wireless-G PCI Adapter that can be used to sniff traffic coming from other computers in my house.  I am using Ethereal 0.10.12 and WinCap 3.1.  I am using WEP encryption, and I have the 10 key code.  

The problem is that while Ethereal recognizes the Linksys Wireless-G PCI Adapter, it does not see the traffic picked up by the antenna on that adapter.  It is not recognizing any packets.

What can I do to solve this problem?  Do I need a new driver for the Linksys Wireless-G PCI Adapter?  I think I have the latest one installed.  Is there a tweak that I can do on my Windows Network?  Is the Ethereal/WinCap combination even the correct software to handle this task?

I'm at a loss.

Thanks for your help.

Richard

Answer : sniffing with ethereal and Linksys Wireless-G PCI Adapter

http://www.winpcap.org/misc/faq.htm

The WinPcap device driver was developed to work primarily with Ethernet (10/100/1000) adapters. Support for other MACs was added during the development, but Ethernet remains the most tested one. A pretty complete list of supported adapters is maintained by the AirSnare team at http://www.micro-logix.com/WinPcap/Supported.asp, you are encouraged to use that page to report the results of your experiences with WinPcap.
The overall situation is:

Windows 95/98/ME: the packet driver works ok on Ethernet networks. It works also on PPP WAN links, but with some limitations (for example it is not able to capture the LCP and NCP packets). FDDI, ARCNET, ATM and Token Ring should be supported, however we did not test them because we do not have the hardware.
Windows NT4/2000/XP/2003: the packet driver works ok on Ethernet networks. As for dial-up adapters and VPN connections, read Q5 and Q6.  As in Win9x,  FDDI, ARCNET, ATM and Token Ring are supported, but not tested by us.
Wireless adapters may present problems, because they are not properly supported by the Windows Kernel: some of them are not detected, other don't support promiscuous mode. In the best case, WinPcap is able to see an Ethernet emulation and not the real transiting packets: this means that the 802.11 frames are transformed into fake Ethernet frames before being captured, and that control frames are not received. Again, refer to the http://www.micro-logix.com/WinPcap/Supported.asp to discover if your adapter works. If it doesn't, you can use the trick explained in this video to capture its traffic.