User Tools

Site Tools


injection_test

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
injection_test [2008/06/27 22:39]
netrolller3d Small cleanups: make it more obvious that the mac address is just a placeholder, add proper double-dash workaround, and make both interfaces "wlanX", which is the de-facto standard.
injection_test [2013/04/25 11:17] (current)
jano [Airserv-ng Test] Minor Update
Line 98: Line 98:
  
   * It confirms that the card can inject and successfully communicate with the specified network.   * It confirms that the card can inject and successfully communicate with the specified network.
 +
  
  
Line 106: Line 107:
 Run the following command: Run the following command:
  
-   aireplay-ng -9 -i ath0 wlan0+   aireplay-ng -9 -i wlan1 wlan0
  
 Where: Where:
  
   * -9 means injection test.   * -9 means injection test.
-  * -i ath0 is the interface to mimic the AP and receives packets.+  * -i wlan1 is the interface to mimic the AP and receives packets.
   * wlan0 is the injection interface.   * wlan0 is the injection interface.
  
 The system responds: The system responds:
  
-   11:06:05  wlan0 channel: 9, ath0 channel: 9+   11:06:05  wlan0 channel: 9, wlan1 channel: 9
    11:06:05  Trying broadcast probe requests...    11:06:05  Trying broadcast probe requests...
    11:06:05  Injection is working!    11:06:05  Injection is working!
Line 122: Line 123:
        
    11:06:05  Trying directed probe requests...    11:06:05  Trying directed probe requests...
-   11:06:05  00:14:6C:7E:40:80 - channel: 9 - 'teddy'+   11:06:05  00:de:ad:ca:fe:00 - channel: 9 - 'teddy'
    11:06:05  Ping (min/avg/max): 2.763ms/4.190ms/8.159ms    11:06:05  Ping (min/avg/max): 2.763ms/4.190ms/8.159ms
    11:06:07  26/30: 87%    11:06:07  26/30: 87%
Line 135: Line 136:
 Analysis of the response: Analysis of the response:
  
-  * **11:06:05  wlan0 channel: 9, ath0 channel: 9**: It is import to make sure both your cards are on the same channel otherwise the tests will not work correctly.+  * **11:06:05  wlan0 channel: 9, wlan1 channel: 9**: It is import to make sure both your cards are on the same channel otherwise the tests will not work correctly.
   * The first part of the output is identical to what has been presented earlier.   * The first part of the output is identical to what has been presented earlier.
   * The last part shows that wlan0 card is able to perform all attack types successfully.   * The last part shows that wlan0 card is able to perform all attack types successfully.
Line 142: Line 143:
 ==== Airserv-ng Test ==== ==== Airserv-ng Test ====
  
-Run the following command:+Run Airserv-ng: 
 + 
 +   airserv-ng -d wlan0 
 + 
 +The system responds: 
 + 
 +   Opening card wlan0 
 +   Setting chan 1 
 +   Opening sock port 666 
 +   Serving wlan0 chan 1 on port 666 
 + 
 +Then run the following command:
  
    aireplay-ng -9 127.0.0.1:666    aireplay-ng -9 127.0.0.1:666
Line 187: Line 199:
 ==== General ==== ==== General ====
  
-Make sure the card(s) are on the same channel as your AP.  You can use iwconfig to confirm which channel your card is currently on.+  * Make sure you use the correct interface name.  For mac80211 drivers, it is typically "mon0" For madwifi-ng, it is typically "ath0" As well, ensure you don't have multiple monitor interfaces created meaning "mon0", "mon1", etc. is bad and the extra interfaces need to be destroyed.
  
-Make sure your card is not channel hopping.+  * Make sure the card(s) are on the same channel as your AP and locked on this channel.  When putting your card into monitor mode, be sure to specify the channel via airmon-ng.  You can use iwconfig to confirm which channel your card is currently on.  The injection test will fail if your card and access point are on different channels.
  
 +  * Make sure your card is not channel hopping.  A very common mistake is to have airodump-ng running in channel hopping mode.  If you use airodump-ng, be sure to use the "-c <channel>" option.  Additionally, ensure all network managers and similar are killed off.
  
 ==== "Network is down" error message ==== ==== "Network is down" error message ====
injection_test.1214599199.txt.gz · Last modified: 2008/06/27 22:39 by netrolller3d