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
airserv-ng [2007/06/20 21:27]
darkaudax added connectivity troubleshooting tip
airserv-ng [2009/09/26 20:46] (current)
darkaudax Fixed typos
Line 1: Line 1:
-====== ​Airtun-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 58: Line 48:
  
 **Debug level of 3**\\ **Debug level of 3**\\
-Contents: Displays a message each time a packet is sent to the client. ​ The packet length is indicated as well.  This level includes ​all the level 1 and level 2 messages.+Contents: Displays a message each time a packet is sent to the client. ​ The packet length is indicated as well.  This level includes ​both the level 1 and level 2 messages.
  
 Examples: Examples:
Line 68: Line 58:
 ===== Usage Examples ===== ===== Usage Examples =====
  
-For all uses, you must first put your wireless card into monitor mode using [[airmon-ng]] or a similar technique.+In all cases, you must first put your wireless card into monitor mode using [[airmon-ng]] or a similar technique.
  
  
Line 96: Line 86:
   airodump-ng 127.0.0.1:​666   airodump-ng 127.0.0.1:​666
  
-It will start scaning ​all networks.+It will start scanning ​all networks.
  
  
Line 121: Line 111:
 At this point you may use any of the aircrack-ng suite programs on the second system and specify "​192.168.0.1:​666"​ instead of the network interface. ​ 192.168.0.1 is the IP address of the server system and 666 is the port number that the server is running on. Remember that 666 is the default port number. At this point you may use any of the aircrack-ng suite programs on the second system and specify "​192.168.0.1:​666"​ instead of the network interface. ​ 192.168.0.1 is the IP address of the server system and 666 is the port number that the server is running on. Remember that 666 is the default port number.
  
-On the second system, you would enter "​airodump-ng 192.168.0.1:​666"​ to start scaning ​all the networks. You may run aircrack-ng applications on as many other systems as you want by simply specifying "​192.168.0.1:​666"​ as the network interface.+On the second system, you would enter "​airodump-ng 192.168.0.1:​666"​ to start scanning ​all the networks. You may run aircrack-ng applications on as many other systems as you want by simply specifying "​192.168.0.1:​666"​ as the network interface.
  
 Example: Example:
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 present, 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.1182367651.txt.gz · Last modified: 2007/06/20 21:27 by darkaudax