wesside-ng
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revision Both sides next revision | ||
|
wesside-ng [2009/09/08 01:20] mister_x removed availability warning (1.0 is released) |
wesside-ng [2009/09/25 23:01] darkaudax Fixed typos |
||
|---|---|---|---|
| Line 22: | Line 22: | ||
| There are a few known limitations: | There are a few known limitations: | ||
| - | * Only open authentication is support. Shared key authentication is not supported. | + | * Only open authentication is supported. Shared key authentication is not supported. |
| * Only B and G networks are supported. | * Only B and G networks are supported. | ||
| * Fake MAC functionality is broken if there is a lot of traffic on the network. | * Fake MAC functionality is broken if there is a lot of traffic on the network. | ||
| Line 40: | Line 40: | ||
| *-f Allows the highest channel for scanning to be defined. Defaults to channel 11. (Optional) | *-f Allows the highest channel for scanning to be defined. Defaults to channel 11. (Optional) | ||
| *-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) | *-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) | + | *-p Determines the minimum number of bytes of PRGA which are gathered. Defaults to 128 bytes. (Optional) |
| *-t For each number of IVs specified, restart the airecrack-ng PTW engine. (Optional) | *-t For each number of IVs specified, restart the airecrack-ng PTW engine. (Optional) | ||
| *-v Wireless access point MAC address (Optional) | *-v Wireless access point MAC address (Optional) | ||
| - | When you run wesside-ng, it creates three files automatically in the current directory when run the program: | + | When you run wesside-ng, it creates three files automatically in the current directory: |
| * wep.cap - The packet capture file. It contains the full packet, not just the IVs. | * wep.cap - The packet capture file. It contains the full packet, not just the IVs. | ||
| Line 153: | Line 153: | ||
| There are a few known limitations: | There are a few known limitations: | ||
| - | * Only open authentication is support. Shared key authentication is not supported. | + | * Only open authentication is supported. Shared key authentication is not supported. |
| * Only B and G networks are supported. | * Only B and G networks are supported. | ||
| * Fake MAC functionality is broken if there is a lot of traffic on the network. | * Fake MAC functionality is broken if there is a lot of traffic on the network. | ||
| - | ==== "ERROR Max retransmists" message ==== | + | ==== "ERROR Max retransmits" message ==== |
| You get an error similar to the following while running the program: | You get an error similar to the following while running the program: | ||
| - | [18:23:49] ERROR Max retransmists for (30 bytes): | + | [18:23:49] ERROR Max retransmits for (30 bytes): |
| B0 00 FF 7F 00 1A 70 51 B0 70 00 0E 2E C5 81 D3 00 1A 70 51 B0 70 00 00 00 00 01 00 00 00 | B0 00 FF 7F 00 1A 70 51 B0 70 00 0E 2E C5 81 D3 00 1A 70 51 B0 70 00 00 00 00 01 00 00 00 | ||
| This can be caused if the AP does not acknowledge the the packets you are sending. Try getting closer to the AP. | This can be caused if the AP does not acknowledge the the packets you are sending. Try getting closer to the AP. | ||
| - | 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. | + | Another reason is that the internal state machine of wesside-ng is confused. This typically happens when there are 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 ==== | + | ==== RT73 chipset and "ERROR Max retransmits" 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. | 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. | ||
| Line 176: | Line 176: | ||
| ==== Known Bugs ==== | ==== Known Bugs ==== | ||
| - | There are are a variety of known bugs which are outlined below. As well, the state engine is known to be broken and this leads to unpredictable results. | + | There are a variety of known bugs which are outlined below. Additionally, the state engine is known to be broken and this leads to unpredictable results. |
| Errors in wesside-ng with madwifi-ng | Errors in wesside-ng with madwifi-ng | ||
wesside-ng.txt ยท Last modified: 2018/03/11 18:57 by mister_x
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
