Install the following via macports:
Install the following via pkg:
wget http://download.aircrack-ng.org/aircrack-ng-1.2.tar.gz tar -zxvf aircrack-ng-1.2.tar.gz cd aircrack-ng-1.2 autoreconf -i ./configure --with-experimental make make install
Commands are exactly the same as Linux but instead of make, use gmake (or CC=gcc5 or any other installed gcc version).
Note: Compilation parameters can also be used with the sources from our subversion repository.
git clone https://github.com/aircrack-ng/aircrack-ng cd aircrack-ng autoreconf -i ./configure make make install
wget http://download.aircrack-ng.org/aircrack-ng-0.9.3.tar.gz tar -zxvf aircrack-ng-0.9.3.tar.gz cd aircrack-ng-0.9.3 make make install
When configuring, the following flags can be used and combined to adjust the suite to your choosing:
After you do “make install” then try to use any of the Aircrack-ng suite commands, you get the error message “command not found” or similar. Your system will look for the Aircrack-ng commands in the directories defined by the PATH command.
Normally, the Aircrack-ng suite programs and man pages are placed in:
/usr/local/bin /usr/local/sbin /usr/local/man
On your system, to determine which directories have the Aircrack-ng programs enter the following. If using “locate” be sure to first run “updatedb”.
locate aircrack-ng locate airmon-ng
find / -name aircrack-ng find / -name airmon-ng
Once you know the directories (exclude the source directories) then determine which directories are in your PATH. To see which directories are included in PATH on your particular system enter:
It should show something like:
At this point compare the actual locations with the directories in your PATH. If the directories are missing from your PATH then you have a few options:
http://www.linuxheadquarters.com/howto/basic/path.shtml http://www.cyberciti.biz/faq/howto-print-path-variable/ http://www.troubleshooters.com/linux/prepostpath.htm http://linux.about.com/od/linux101/l/blnewbie3_1_4.htm
On Debian-based distros, if you get something similar to:
/bin/sh: line 0: cd: /lib/modules/2.6.15-28-amd64-generic/build: No such file or directory Makefile.inc:66: *** /lib/modules/2.6.15-28-amd64-generic/build is missing, please set KERNELPATH. Stop.
The build directory gets installed together with the kernel headers, so either you lack the correct headers or your KERNELPATH is wrong. Please check that `uname -r` returns “2.6.15-28-amd64-generic”.
Do a “sudo apt-get install linux-headers-`uname -r`” or just “sudo apt-get install linux-headers”.
If uname returns exactly that string and the current headers are installed, the remove the headers and install them again. Also check /usr/src for installed header files, maybe it got mixed up for whatever reason.
In the above examples, needless to say, change “2.6.15-28-amd64-generic” to whatever you are running.
If you get something similar to:
crypto.h:12:26: error: openssl/hmac.h: No such file or directory crypto.h:13:25: error: openssl/sha.h: No such file or directory crypto.h:15:25: error: openssl/rc4.h: No such file or directory crypto.h:16:25: error: openssl/aes.h: No such file or directory
Solution: You are missing the OpenSSL development package. Depending on the distribution, download and install openssl-devel or libssl-devel (libssl-dev /Ubuntu/). Or worst case, install it from source: http://www.openssl.org.
If you get something similar to:
wesside-ng.c:54:18: error: zlib.h: No such file or directory
Solution: You are missing the zlib development package. Depending on the distribution, download and install zlib-devel. Or worst case, install it from source: http://www.zlib.net.
You get something similar to:
radiotap-parser.h:29: error: conflicting types for ‘__le64’ /usr/include/linux/types.h:158: error: previous declaration of ‘__le64’ was here
See this thread for a solution.
Open your package manager and install 'Aircrack-ng' package. Be sure to check that the version offered is up-to-date – you may see problems with older versions, especially if you have a card for which support was added recently, e.g. ACX, Broadcom or Intel. Ubuntu and Debian are particularly problematic in this matter.
The Windows version of the Aircrack-ng suite does not have an install program. You must manually install (unzipping archive) the software.
Here are the steps to follow for Windows XP:
Prior to using the software, make sure to install the drivers for your particular wireless card. See this link for the instructions.
To now use the Aircrack-ng suite, start Windows Explorer and double click on Aircrack-ng GUI.exe inside “bin” subdirectory. The GUI requires .NET Framework 2.0 to run (.NET Frameworks 1.0/1.1 are not able to run this executable, 2.0 or better MUST be installed).
Alternatively, open a command prompt (Start menu → Execute → cmd.exe) and change to the “C:\aircrack-ng-0.9-win\bin” directory and execute the individual commands.
Important note: airodump-ng and aireplay-ng will not work under OSX natively. Which means, injection and capture will have to use other means. If you have an intel Mac (any recent-ish Mac is), check out the VMware Fusion option which is mentioned lower on this page.
The simplest and easiest way to install on Mac OS X is via Macports. You simply do “sudo port install aircrack-ng”.
Alternatively, use the following instructions:
Optional is openssl-dev and sqlite3 which can be installed through fink
See this thread for instructions on installing and using the Aircrack-ng suite on OpenBSD.
Important Note: Virtualization solutions (VMware/VirtualBox/Virtual PC/…) only work with USB cards. Card that are PCI/MiniPCI/PCMCIA/CardBus/Express Card/PCI Express/PCI-X/MiniPCI Express won't work at all.
Important note: VMWare Workstation 6.5 (and maybe Player 2.5 too) is known not to work correctly with rtl8187 driver. It uses the whole CPU and it seems to be hanging (it is really slow) for an unknown reason.
On VMware Player, the device should be shown in the title bar, click on it to activate it. On VMware Workstation, use menu “VM –> Removable devices –> USB” and then select the device:
It will automatically unplug the device from Windows and attach it to the virtual machine.