airserv-ng
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionLast revisionBoth sides next revision | ||
airserv-ng [2007/05/07 23:09] – created: preliminary documentation for airserv-ng darkaudax | airserv-ng [2009/09/08 01:20] – removed availability warning (1.0 is released) mister_x | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | + | ||
- | ++++++ IMPORTANT ++++++\\ | + | |
- | ++++++ IMPORTANT ++++++\\ | + | |
- | ++++++ IMPORTANT ++++++\\ | + | |
- | + | ||
- | This functionality will be available in a future release. It is NOT available currently. | + | |
- | + | ||
- | ++++++ IMPORTANT ++++++\\ | + | |
- | ++++++ IMPORTANT ++++++\\ | + | |
- | ++++++ IMPORTANT ++++++\\ | + | |
===== Description ===== | ===== Description ===== | ||
- | Airserv-ng is wireless card server which allows multiple wireless application programs to independently use a wireless card via a client-server TCP network connection. | + | Airserv-ng is a wireless card server which allows multiple wireless application programs to independently use a wireless card via a client-server TCP network connection. |
- | When the server is started, it listens on a specific | + | When the server is started, it listens on a specific IP and TCP port number for client connections. |
This allows for a number of interesting possibilities: | This allows for a number of interesting possibilities: | ||
- | * By eliminating the wireless card/driver complexity, | + | * By eliminating the wireless card/driver complexity, software developers |
* Remote sensors are now easy to implement. | * Remote sensors are now easy to implement. | ||
* You can mix and match operating systems. | * You can mix and match operating systems. | ||
Line 39: | Line 29: | ||
==== Debug Levels ==== | ==== Debug Levels ==== | ||
- | There are three debug levels. | + | There are three debug levels. |
**Debug level of 1**\\ | **Debug level of 1**\\ | ||
- | Contents: Shows connection | + | Contents: Shows connect |
Examples: | Examples: | ||
Line 50: | Line 40: | ||
**Debug level of 2**\\ | **Debug level of 2**\\ | ||
- | Contents: Shows channel change requests and invalid client command requests in addition to the debug level 1 messages. | + | Contents: Shows channel change requests and invalid client command requests in addition to the debug level 1 messages. |
Examples: | Examples: | ||
Line 69: | Line 59: | ||
For all uses, you must first put your wireless card into monitor mode using [[airmon-ng]] or a similar technique. | For all uses, you must first put your wireless card into monitor mode using [[airmon-ng]] or a similar technique. | ||
+ | |||
Line 90: | Line 81: | ||
| | ||
- | At this point you may use any of the aircrack-ng suite programs and specify " | + | At this point you may use any of the aircrack-ng suite programs and specify " |
+ | |||
+ | Example: | ||
+ | airodump-ng 127.0.0.1: | ||
+ | |||
+ | It will start scaning all networks. | ||
- | For example: You could enter " | ||
==== Remote machine ==== | ==== Remote machine ==== | ||
- | This scenario has the server running on one system with an IP address of 192.168.0.15 and the applications | + | This scenario has the server running on one system with an IP address of 192.168.0.1 and the applications |
Start the program with: | Start the program with: | ||
Line 105: | Line 100: | ||
Where: | Where: | ||
- | * -d ath0 is the network card to use. Specify the network interface for your particular card. | + | * -d ath0 is the network card to use. Specify the network interface for your particular card. |
The system responds: | The system responds: | ||
Line 114: | Line 109: | ||
| | ||
- | At this point you may use any of the aircrack-ng suite programs on the second system and specify " | + | At this point you may use any of the aircrack-ng suite programs on the second system and specify " |
- | On the second system, you would enter " | + | On the second system, you would enter " |
+ | Example: | ||
+ | |||
+ | airodump-ng -c 6 192.168.0.1: | ||
===== Usage Tips ===== | ===== Usage Tips ===== | ||
None at this time. | None at this time. | ||
- | |||
===== Usage Troubleshooting ===== | ===== Usage Troubleshooting ===== | ||
Is your card in monitor mode? Make sure your card is in monitor mode prior to starting airserv-ng. | Is your card in monitor mode? Make sure your card is in monitor mode prior to starting airserv-ng. | ||
+ | |||
+ | Are you connecting to the correct IP and TCP port number? | ||
Firewall software can block communication so make sure the following allows communication to and from the server port. This applies to both the machine running airserv-ng and the client machine. | Firewall software can block communication so make sure the following allows communication to and from the server port. This applies to both the machine running airserv-ng and the client machine. | ||
Line 143: | Line 142: | ||
* Under linux: " | * Under linux: " | ||
* Under Window, open a command line and type " | * Under Window, open a command line and type " | ||
+ | |||
+ | At the present time, there are known issues with the madwifi-ng drivers for atheros-based cards. | ||
airserv-ng.txt · Last modified: 2009/09/26 20:46 by darkaudax