Differences

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

--- wesside-ng [2008/02/08 01:44] – added -k parameter documentation darkaudax
+++ wesside-ng [2008/02/08 16:06] – fixed typos darkaudax
@@ Line 51: / Line 51: @@
   *-c              Do not start aircrack-ng.  Simply capture the packets until control-C is hit to stop the program!  (Optional)
   *-f              Allows the highest channel for scanning to be defined.  Defaults to channel 11. (Optional)
-  *-k              Ignores ACKs since some cards do not report them.  It will therefore automatically retransmit X times.  That is, -k 1 will transmit once and assume the packet gets there.  -k 2 will retransmit twice, and so on.  Note: The higher the -k value, the slower transmission rate will be due to the many retransmits.
+  *-k              Ignores ACKs since some cards/drivers do not report them.  It will therefore automatically retransmit X times.  That is, -k 1 will transmit once and assume the packet gets there.  -k 2 will retransmit twice, and so on.  Note: The higher the -k value, the slower transmission rate will be due to the many retransmits.  (Optional)
   *-p              Determines the minimum number of bytes of PRGA which is gathered.  Defaults to 128 bytes.  (Optional)
   *-t              For each number of IVs specified, restart the airecrack-ng PTW engine. (Optional)
@@ Line 140: / Line 140: @@
 ===== Usage Tips =====
-None at this time.
+==== Using the -k option ====
+Some cards/drivers do not properly report ACKs.  The "-k" option allows ACKs to be ignored and forces wesside-ng to retransmit the packets the number of times specified.  It will therefore automatically retransmit X times.  That is, -k 1 will transmit once and assume the packet gets there.  -k 2 will retransmit twice, and so on.  Note: The higher the -k value, the slower transmission rate will be due to the many retransmits.
+Some specific cases:
+  * If you get MAX retransmits error, try -k 1.
+  * If you have a poor connection, try -k 3.
+In general, you can experiment with different values to determine if it resolves the problem.  There is no right or wrong value.
@@ Line 171: / Line 179: @@
 Another reason is that the internal state machine of wesside-ng is confused.  This typically happens when there is other wireless packets picked up and the state machine does not properly interpret them.  Remember, this is still proof-of-concept code and not completely stable.  Just try rerunning wesside-ng.
+==== RT73 chipset and "ERROR Max retransmists" message ====
+If you are using the RT73 chipset, try adding the "-k 1" option.  The driver for this chipset does not properly report ACKs.  Using the "-k 1" option gets around this.
 ==== Known Bugs ====