Yes, we are aware of this limitation. The capture component of WinPcap is a protocol driver, that relies on the network interface card (NIC) driver to obtain the raw packets. This allows hardware independency and avoids writing a different driver for every NIC. However some NIC drivers, like for example 802.11b or PPP ones, don't deliver to the protocols the actual packets, but a subset of them. As a consequence, WinPcap-bases apps are not able to see control and management packets of wireless networks. Solving the problem requires writing a NIC driver for a particular 802.11b card. Some commercial solutions adopt this strategy, but it obviously requires a lot of resources, i.e. a lot of of money...
Loris ----- Original Message ----- From: "C D" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, April 04, 2002 3:28 AM Subject: [WinPcap-users] WinPCap and 802.11 frames > Hi, I tried using WinPcap Version 2.3, together with Ethereal packet capture > to check whether it can capture Wireless IEEE 802.11b control and management > frames, but it doesn't capture those packets. > > I have an access point around me which continuously broadcasts Beacon frames > but WinpCap and Ethereal doesn't capture and display the raw MAC frames on > the screen. > > Are you aware of this limitation in the WinpCap? If this is a limitation, do > you know why WinpCap can't capture these IEEE 802.11b MAC frames? > > Thank you for your help. > > Regards, > Abel > > > > _________________________________________________________________ > MSN Photos is the easiest way to share and print your photos: > http://photos.msn.com/support/worldwide.aspx > >
