aireplay-ng
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
aireplay-ng [2009/09/25 19:58] – Fixed typos and update to reflect 1.0 version darkaudax | aireplay-ng [2022/02/09 00:44] (current) – [Description] update mister_x | ||
---|---|---|---|
Line 6: | Line 6: | ||
With the [[packetforge-ng]] tool it's possible to create arbitrary frames. | With the [[packetforge-ng]] tool it's possible to create arbitrary frames. | ||
- | Most drivers needs to be patched to be able to inject, don't forget to read [[install_drivers|Installing drivers]]. | + | Some drivers needs to be patched to be able to inject, don't forget to read [[install_drivers|Installing drivers]]. |
===== Usage of the attacks ===== | ===== Usage of the attacks ===== | ||
Line 18: | Line 18: | ||
* Attack 4: [[KoreK chopchop|KoreK chopchop attack]] | * Attack 4: [[KoreK chopchop|KoreK chopchop attack]] | ||
* Attack 5: [[Fragmentation|Fragmentation attack]] | * Attack 5: [[Fragmentation|Fragmentation attack]] | ||
- | * Attack 6: Caffe-latte attack | + | * Attack 6: [[cafe-latte|Cafe-latte attack]] |
- | * Attack 7: Client-oriented fragmentation attack | + | * Attack 7: [[hirte|Client-oriented fragmentation attack]] |
+ | * Attack 8: [[WPA Migration Mode]] | ||
* Attack 9: [[injection_test|Injection test]] | * Attack 9: [[injection_test|Injection test]] | ||
===== Usage ===== | ===== Usage ===== | ||
- | This section provides a general overview. | + | This section provides a general overview. |
Usage: | Usage: | ||
Line 45: | Line 46: | ||
*-w iswep : frame control, WEP bit | *-w iswep : frame control, WEP bit | ||
- | When replaying (injecting) packets, the following options apply. | + | When replaying (injecting) packets, the following options apply. |
Replay options: | Replay options: | ||
Line 128: | Line 129: | ||
These items apply to all modes of aireplay-ng. | These items apply to all modes of aireplay-ng. | ||
+ | |||
+ | ==== aireplay-ng does not inject packets ==== | ||
+ | Ensure you are using the correct monitor mode interface. | ||
==== For madwifi-ng, ensure there are no other VAPs running ==== | ==== For madwifi-ng, ensure there are no other VAPs running ==== | ||
Line 232: | Line 236: | ||
For all of the above, running airodump-ng and the related text file should provide all the information you require identify and correct the problem. | For all of the above, running airodump-ng and the related text file should provide all the information you require identify and correct the problem. | ||
+ | |||
+ | |||
+ | ==== interfaceX is on channel Y, but the AP uses channel Z ==== | ||
+ | |||
+ | A typical example of this message is: "mon0 is on channel 1, but the AP uses channel 6" | ||
+ | |||
+ | This means something is causing your card to channel hop. Possible reasons is that failed to start airodump-ng locked to a single channel. | ||
+ | |||
+ | Another reason is that you have processes such as a network manager or wpa_supplicant channel hopping. | ||
==== General ==== | ==== General ==== | ||
Line 247: | Line 260: | ||
* If Prism2, make sure the firmware was updated. | * If Prism2, make sure the firmware was updated. | ||
* Ensure your are running the current stable version. | * Ensure your are running the current stable version. | ||
- | * It does not hurt to check the [[http://trac.aircrack-ng.org/|Trac System]] to see if your " | + | * It does not hurt to check the [[https://github.com/aircrack-ng/ |
- | ===== Release Candidate or SVN Version Notes ===== | ||
- | |||
- | This section ONLY applies the latest SVN version and to some release candidate versions of the aircrack-ng suite. | ||
- | |||
- | Changes: | ||
- | |||
- | * "-e < | ||
- | * " | ||
- | * " | ||
- | * " | ||
- | * " | ||
- | * " | ||
aireplay-ng.1253901522.txt.gz · Last modified: 2009/09/25 19:58 by darkaudax