Pegasus wrote:
The problems I am facing are: 1) How do I transfer the rf information to ethereal (WinPcap seems to be converting wireless packet to fake Ethernet packets do not have those fields)
No. It's not WinPcap that's doing with that.
If you capture with Ethereal - or WinDump, or Analyzer, or... - on an 802.11 interface on Windows, the 802.11 adapter, or the driver for the adapter, converts the 802.11 header to an Ethernet header, as that's what 802.11 miniport NDIS drivers are expected to do:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/network/hh/network/213_802.11_f36ba76d-a4ea-4d78-ae03-0517b31a2c6a.xml.asp
"In addition, packets sent to or received from the driver must be in 802.3 format. The driver translates the 802.3 media access control (MAC) header of outgoing packets to the appropriate 802.11 MAC header before passing the packets to the underlying network interface card (NIC). Similarly, the driver translates the 802.11 MAC header of incoming packets to the appropriate 802.3 MAC header before indicating the packets to the NDIS layer."
I would like to capture in etheral the following fields : Signal, channel, rate, noise, actual time of getting aired and not the time at which it reaches the windows.
In order to do that, you will have to supply the packet to WinPcap by some other mechanism than NDIS, which is how WinPcap expects to receive packets.
2) In what format does my card/driver dump packets to the winpcap and how does it inform at packet arrival?
It happens through NDIS. In order to do what you want, WinPcap would have to be modified to receive packets from your driver via some mechanism other than NDIS.
================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/winpcap-users@winpcap.polito.it/
To unsubscribe use mailto: [EMAIL PROTECTED]
==================================================================
