injection_test
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
injection_test [2008/06/21 13:33] – Clarified monitor mode is required. darkaudax | injection_test [2013/04/25 11:17] (current) – [Airserv-ng Test] Minor Update jano | ||
---|---|---|---|
Line 24: | Line 24: | ||
An additional feature is the ability to test connectivity to [[airserv-ng]]. | An additional feature is the ability to test connectivity to [[airserv-ng]]. | ||
+ | |||
===== Usage ===== | ===== Usage ===== | ||
- | aireplay-ng -9 -e teddy -a 00:14:6C:7E:40:80 -i wlan0 ath0 | + | aireplay-ng -9 -e teddy -a 00:de:ad:ca:fe:00 -i wlan1 wlan0 |
Where: | Where: | ||
- | * -9 means injection test. Long form is - -test. | + | * -9 means injection test. Long form is -'''' |
* -e teddy is the network name (SSID). | * -e teddy is the network name (SSID). | ||
- | * -a 00:14:6C:7E:40:80 ath0 is MAC address of the access point (BSSID). This is optional. | + | * -a 00:de:ad:ca:fe:00 ath0 is MAC address of the access point (BSSID). This is optional. |
- | * -i wlan0 is interface name of the second card if you want to determine which attacks your card supports. | + | * -i wlan1 is interface name of the second card if you want to determine which attacks your card supports. |
- | * ath0 is the interface name or airserv-ng IP Address plus port number. | + | * wlan0 is the interface name or airserv-ng IP Address plus port number. |
IMPORTANT: | IMPORTANT: | ||
Line 97: | 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 105: | Line 107: | ||
Run the following command: | Run the following command: | ||
- | | + | |
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: | ||
- | | + | |
| | ||
| | ||
Line 121: | Line 123: | ||
| | ||
- | | + | |
| | ||
| | ||
Line 134: | Line 136: | ||
Analysis of the response: | Analysis of the response: | ||
- | * **11: | + | * **11: |
* 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 141: | Line 143: | ||
==== Airserv-ng Test ==== | ==== Airserv-ng Test ==== | ||
- | Run the following command: | + | Run Airserv-ng: |
+ | |||
+ | | ||
+ | |||
+ | The system responds: | ||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | Then run the following command: | ||
| | ||
Line 186: | Line 199: | ||
==== General ==== | ==== General ==== | ||
- | Make sure the card(s) are on the same channel as your AP. | + | * Make sure you use the correct interface name. |
- | Make sure your card is not channel | + | * Make sure the card(s) are on the same channel as your AP and locked on this channel. |
+ | * Make sure your card is not channel hopping. | ||
==== " | ==== " |
injection_test.1214048014.txt.gz · Last modified: 2008/06/21 13:33 by darkaudax