A Descriptive Title

A Descriptive Title

Installing
==========

This version now requires more libraries than 0.X versions to be compiled.
See INSTALLING file for more information

OpenWrt Devices
===============

You can use airodump-ng on OpenWrt devices. You'll have to use specify
prism0 as interface. Airodump-ng will automatically create it.
Rq: Aireplay DOESN'T work on OpenWrt (2.4 kernel) with broadcom chipset since the driver doesn't support injection. It *may* work with 2.6 kernels >= 2.6.24 (kamikaze 8.09+ custom-built).

Known bugs:
===========

Drivers
-------

Madwifi-ng
----------

The cause of most of these problems (1, 2 and 3) is that Madwifi-ng cannot easily change the rate in monitor mode.
Technically, when changing rate while in monitor mode, the raw socket gets invalidated and we have to get it again.
Madwifi-ng is getting replaced by several drivers: ath5k, ath9k and ar9170.


Problem 1: No client can associate to an airbase soft AP.
Solution 1: None at this time.


Problem 2: When changing rate while you are capturing packet makes airodump-ng stall
Solution 2: Restart airodump-ng or change rate before starting it.

Problem 3: After some time it stops capturing packets and you're really sure no network manager are running at all.
Solution 3: That's a known bug in the driver, it may happen at any time (the time before it fails can vary a lot:
            from 5 minutes to 50 or even more). Try (as root) unloading completely the driver with 'madwifi-unload'
            and then run 'modprobe ath_pci autocreate=monitor'.
 

Problem 4: When creating a new VAP airodump-ng takes up to 10-15 seconds to see the first packet
Solution 4: It's the behaviour of madwifi-ng, don't worry (... be happy ;)).

Orinoco
-------

Problem: BSSID is not reported correctly or is 00:00:00:00:00:00 or signal is not reported correctly.
Solution: None. Consider replacing your card, orinoco is really really old.

Aircrack-ng...