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

Ardilla- New tool for finding SQL Injection and XSS

Three Researchers -- MIT's Adam Kiezun , Stanford's Philip Guo , and Syracuse University's Karthick Jayaraman -- has developed a new tool ' Ardilla ' that automatically finds and exploits SQL injection and cross-site scripting vulnerabilities in Web applications. It creates inputs that pinpoint bugs in Web applications and then generates SQL injection and XSS attacks. But for now Ardilla is for PHP -based Web app only. The researchers say Ardilla found 68 never-before found vulnerabilities in five different PHP applications using the tool -- 23 SQL injection and 45 XSS flaws. More information is awaited. For their attack generation techniques refer to their document at: http://www.cs.washington.edu/homes/mernst/pubs/create-attacks-tr054.pdf

File Upload through Null Byte Injection

Sometimes, during file upload we come across situation wherein there would be check on the file extension at the client side as well as server side too. If the application does allow only .jpeg extension to be uploaded, the client side java script checks for the extension of the file before passing the request. We all know that how easily this can be defeated. Some applications, checks for the extension at the server side also. That's not easy to bypass. However there are some ways with which it still can be bypassed. Most of server side scripts are written in high level languages such as Php, Java etc who still use some C/C++ libraries to read the file name and contents. That leads to the problem. In C/C++ a line ends with /00 or which is called Null Byte. So whenever the interpreter sees a null byte at the end of the a string, it stops reading thinking it has reached at the end of the string. This can be used for the bypass. It works for many servers, specially php servers. T

Combining power of Fiddler with Burp

Both are pretty powerful tools when it comes to intercept and modify http communications. But at some point of time, they become even more powerful combo if tied with each other. They complement each other. In a recent pentest I came across a similar situation where in Burp was not able to intercept a specific kind of traffic and Fiddler came to rescue. The application was designed to upload video. The initial communication was straight forward, I mean logging into application, filling up the video details etc. And all these were easily captured by Burp except the point where you hit the Upload Video and it connects to a different server and surprisingly it was not captured by Burp, not sure why, even after repeated attempts. So, I fired Fiddler to see if the it sees this request. But it's a;ways to play with requests using Burp due to it's various functionalities like, Intruder, Repeaters etc. But it was necessary to capture this request in Burp. So the below steps can be