airtun-ng
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
airtun-ng [2009/08/17 00:29] – Add WDS support aspj | airtun-ng [2010/03/07 23:36] – Fixed typo darkaudax | ||
---|---|---|---|
Line 25: | Line 25: | ||
*-t tods : send frames to AP (1) or to client (0) (optional / defaults to 0) | *-t tods : send frames to AP (1) or to client (0) (optional / defaults to 0) | ||
*-r file : read frames out of pcap file (optional) | *-r file : read frames out of pcap file (optional) | ||
+ | *-h MAC : source MAC address | ||
+ | *-H : Display help. Long form --help | ||
Repeater options (the following all require double dashes): | Repeater options (the following all require double dashes): | ||
Line 30: | Line 32: | ||
*- -bssid <mac> : BSSID to repeat. | *- -bssid <mac> : BSSID to repeat. | ||
*- -netmask < | *- -netmask < | ||
+ | |||
===== Scenarios ===== | ===== Scenarios ===== | ||
Line 53: | Line 56: | ||
| | ||
- | This interface (at0) will receive a copy of every wireless network packet. The packets will have been decrypted with the key you have provided. | + | This interface (at0) will receive a copy of every wireless network packet. The packets will have been decrypted with the key you have provided. |
==== WEP injection ==== | ==== WEP injection ==== | ||
Line 153: | Line 156: | ||
Please note that the file contents are transmitted exactly as is. You may ignore the message " | Please note that the file contents are transmitted exactly as is. You may ignore the message " | ||
+ | |||
+ | ==== Tunneling traffic into WDS networks or WiFi Bridges ==== | ||
+ | |||
+ | If you use a recent version of airtun-ng, you can use its WDS support to inject traffic into WDS networks and WiFi bridges. | ||
+ | Bridges are pretty secure since traffic may be sniffed, but it is impossible to connect with them to send data into the networks. | ||
+ | This is where airtun-ng comes into the game. With airtun-ng you can impersonate either of the two endpoints to interact with the other one. Lets assume you can only see one node of the bridge, this is how you can check if an attacker could inject traffic into this side of the network: | ||
+ | |||
+ | * There are two nodes AA: | ||
+ | * Your attacking client can only send to and receive from node A. | ||
+ | * In this case you will only see packets with Transmitter = A and Receiver = B on your interface. | ||
+ | * If you impersonate node B, you could inject traffic into the network behind node A. | ||
+ | |||
+ | This is how to setup airtun-ng for this scenario: | ||
+ | |||
+ | | ||
+ | |||
+ | If you are able to see both sides of a WDS/Bridge network, you can enable bidirectional mode. This enables communication with both endpoint' | ||
+ | |||
+ | | ||
+ | |||
+ | WDS mode is fully compatible with WEP encryption, so you can use the -w and -y flags as usual. | ||
+ | However, Repeater Mode hasn't been tested with WDS. | ||
===== Usage Tips ===== | ===== Usage Tips ===== | ||
Line 175: | Line 200: | ||
This loads the " | This loads the " | ||
+ | |||
+ | ==== Error creating tap interface: Permission denied ==== | ||
+ | |||
+ | See the following [[faq# | ||
+ |
airtun-ng.txt · Last modified: 2015/04/12 23:15 by mister_x