Differences

This shows you the differences between two versions of the page.

--- airserv-ng [2009/09/08 01:20] – removed availability warning (1.0 is released) mister_x
+++ airserv-ng [2009/09/26 20:46] (current) – Fixed typos darkaudax
@@ Line 48: / Line 48: @@
 **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:
@@ Line 58: / Line 58: @@
 ===== 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 86: / Line 86: @@
   airodump-ng 127.0.0.1:666
-It will start scaning all networks.
+It will start scanning all networks.
@@ Line 111: / 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.
-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:
@@ Line 143: / Line 143: @@
   * 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.
+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.