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
Next revision Both sides next revision
injection_test [2008/06/27 22:42]
netrolller3d Small cleanups, round 2: make it more obvious that the mac address is just a placeholder and make both interfaces "wlanX", which is the de-facto standard.
injection_test [2012/08/17 23:30]
jano [Usage]
Line 34: Line 34:
   * -9 means injection test.  Long form is -''''-test.    * -9 means injection test.  Long form is -''''-test. 
   * -e teddy is the network name (SSID).  This is optional.   * -e teddy is the network name (SSID).  This is optional.
-  * -00:de:ad:ca:fe:00 ath0 is MAC address of the access point (BSSID). This is optional.+  * -00:de:ad:ca:fe:00 ath0 is MAC address of the access point (BSSID). This is optional.
   * -i wlan1 is interface name of the second card if you want to determine which attacks your card supports.  This interfaces acts as an AP and receives packets.  This is optional.   * -i wlan1 is interface name of the second card if you want to determine which attacks your card supports.  This interfaces acts as an AP and receives packets.  This is optional.
   * wlan0 is the interface name or airserv-ng IP Address plus port number.  This interface is used to send packets.  For example - 127.0.0.1:666. (Mandatory)   * wlan0 is the interface name or airserv-ng IP Address plus port number.  This interface is used to send packets.  For example - 127.0.0.1:666. (Mandatory)
Line 188: Line 188:
 ==== 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.txt ยท Last modified: 2013/04/25 11:17 by jano