User Tools

Site Tools


airserv-ng

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
Last revision Both sides next revision
airserv-ng [2007/06/27 03:59]
sc0tch Incorrect Table of contents title.
airserv-ng [2009/09/08 01:20]
mister_x removed availability warning (1.0 is released)
Line 1: Line 1:
 ====== Airserv-ng ====== ====== Airserv-ng ======
- 
-++++++ IMPORTANT ++++++\\ 
-++++++ IMPORTANT ++++++\\ 
-++++++ IMPORTANT ++++++\\ 
- 
-This functionality will be available in a future release. It is NOT available currently. 
- 
-++++++ IMPORTANT ++++++\\ 
-++++++ IMPORTANT ++++++\\ 
-++++++ IMPORTANT ++++++\\ 
  
 ===== Description ===== ===== Description =====
Line 130: Line 120:
  
 None at this time. None at this time.
- 
  
 ===== Usage Troubleshooting ===== ===== Usage Troubleshooting =====
Line 136: Line 125:
 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? ​ Double check this.  Remember that the default port number is 666.  You can use the [[http://​aircrack-ng.org/​doku.php?​id=injection_test#​airserv-ng_test|aireplay-ng injection test]] to verify connectivity and proper operation.+Are you connecting to the correct IP and TCP port number? ​ Double check this.  Remember that the default port number is 666.  You can use the [[injection_test#​airserv-ng_test|aireplay-ng injection test]] to verify connectivity and proper operation.
  
 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. ​ Items to check: 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. ​ Items to check:
Line 153: Line 142:
   * Under linux: "​netstat -an" or "lsof -i" and look for the port number.   * Under linux: "​netstat -an" or "lsof -i" and look for the port number.
   * Under Window, open a command line and type "​netstat -an" then look for the port number.   * Under Window, open a command line and type "​netstat -an" then look for the port number.
 +
 +At the present time, there are known issues with the madwifi-ng drivers for atheros-based cards. ​ Channel hopping and setting the channel does not always work correctly. ​ Very often the card is not set to the requested channel and/or the hopping does not take place.
  
airserv-ng.txt ยท Last modified: 2009/09/26 20:46 by darkaudax