Skip to main content

Using an AirPcap device in Windows with Wireshark

Capturing wireless traffic in a Windows environment is unfortunately not as easy as a setting
change. As with most Windows-based software, drivers in Windows are often not open source and do not allow for configuration change into monitor mode. With this in mind, we must use a specialized piece of hardware known as an AirPcap device.

Once you have obtained an AirPcap device you will be required to install the software on the accompanying CD to your analysis computer.



The configurable options include:
• Interface - Select the device you are using for your capture here. Some advanced analysis scenarios may require you to use more than one AirPcap device to sniff simultaneously on multiple channels.

• Blink LED - Clicking this button will make the LED lights on the AirPcap device blink.
This is primarily used to identify the specific adapter you are using if you are using multiple
AirPcap devices.

• Channel - In this field, you select the channel you want AirPcap to listen on.

Extension Channel - This option is only available on 802.11n capable AirPcap devices (AirPcap nX) and allows you to select an extension channel.
• Capture Type - The options are 802.11 Only, 802.11+Radio, and 802.11+PPI. The 802.11 Only option includes the standard

Include 802.11 FCS in Frames - By default, systems strip the last four checksum
bits from wireless packets.

• FCS Filter - This option will allow you to filter out packets based upon whether they have a
valid or invalid FCS.

AirPcap supports decryption of wireless traffic in two modes. Driver mode, configurable from
the AirPcap Control Panel, only supports WEP.
It is recommend that decryption keys be configured using Wireshark mode, which supports WEP, WPA, and WPA2, and is managed from the wireless toolbar inside of Wireshark.
You can enable this toolbar when you have an AirPcap adapter plugged into your analysis computer by opening Wireshark, going to the View dropdown menu, and placing a checkmark next to the Wireless Toolbar option.

You will need to set the Decryption Mode drop-down box to Wireshark, and add your appropriate encryption key by clicking the Decryption Keys button, clicking New, selecting the key type, and entering the key itself.



Analyzing Wireshark dissection of the 802.11 header:

We can immediately determine this by looking at the Type listing under the Frame Control section of the packet.

Comments

Anonymous said…
dude can we get aircap usb in sp road, wats the cost of the device plz mail further details
zoomzatag

best regards,
zomzzz
Anonymous said…
dude can we get aircap usb in sp road, wats the cost of the device plz mail further details
zoomzatag@gmail.com

best regards,
zomzzz
Amit R Lambi said…
This comment has been removed by the author.
Abhay Tripathi said…
hi Friend

Can you give me an estiaate of the airpcap usb, Also if any contact person name in India would be helpful from whom I can talk about the same.
Anonymous said…
Hello Nilesh,

Can you please let me know about the cost of airpcap device and where I can get in Blore?

Regards,

Popular posts from this blog

Anti CSRF header

Recently I came across an application which was preventing crsf attacks using a unique non-traditional approach. In traditional approach the csrf is thwarted by embedding unique random tokens, called nonce, in each sensitive page. But this application, which was making ajax calls and used jQuery, was creating a header to identify the valid and invalid requests altogether. The idea is to generate a custom header, x-session-token in this case, with every request which is considered sensitive and includes any sort of transaction. For example: xhr.setRequestHeader('x-session-token', csrf_token)   At the server level, server checks for this header if found request is fulfilled, otherwise rejected. We need to use xhr calls for making use of this technique, not useful in regular POST and GET requests. Since, I was not aware of this kind of countermeasures, probably, since most of the applications I did were using standard requests. So, I searched a bit and found even Go...

Some one watching where you visited!

Yes... Mozilla has been susceptible to browser-history stealing java script code. Today, Giorgio posted some cool information about the exploit. Mozilla is already working on this. This bug has been reported. Actually they have set up a web site to show the proof-of-concept. Visit www.statrpanic.com in FF,Safari or Netscape and it will tell you which websites have you been already ! But I am not sure it will work in IE or not because my IE is not responding to the website. Clearing history of visited website makes you safe to this attack. I mean this is one way..may be there are other ways to exploit this. But I have found this effective. Try it yourself in FF and then in IE and see the results.