Aircrack-ng

User Tools

Site Tools

Trace:
aireplay-ng

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
aireplay-ng [2009/09/26 22:02] – Updated to reflect the release of version 1.0 darkaudaxaireplay-ng [2010/02/03 15:57] – Fixed typos darkaudax
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: [[cafe-latte|Cafe-latte attack]] (The documentation will be available shortly.) +    * Attack 6: [[cafe-latte|Cafe-latte attack]] 
-    * Attack 7: [[hirte|Client-oriented fragmentation attack]] (The documentation will be available shortly.)+    * Attack 7: [[hirte|Client-oriented fragmentation attack]]
     * Attack 9: [[injection_test|Injection test]]     * Attack 9: [[injection_test|Injection test]]
  
Line 128: Line 128:
  
 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.  "iwconfig" will show the wireless interfaces and their state.  For the mac80211 drivers, the monitor mode interface is typically "mon0".  For ieee80211 madwifi-ng drivers, it is typically "ath0".  For other drivers, the interface name may vary.
  
 ==== For madwifi-ng, ensure there are no other VAPs running ==== ==== For madwifi-ng, ensure there are no other VAPs running ====
aireplay-ng.txt · Last modified: 2022/02/09 00:44 by mister_x