packetforge-ng
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
packetforge-ng [2007/01/27 20:49] – Standardizing the format darkaudax | packetforge-ng [2007/04/27 16:58] – added examples for v.8 new features darkaudax | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Packetforge-ng ====== | ====== Packetforge-ng ====== | ||
- | |||
- | |||
Line 31: | Line 29: | ||
*-y < | *-y < | ||
- | ====Modes: | + | ====Modes |
*--arp | *--arp | ||
*--udp | *--udp | ||
*--icmp | *--icmp | ||
+ | *--null | ||
*--custom | *--custom | ||
- | |||
===== Usage Example ===== | ===== Usage Example ===== | ||
+ | ==== Generating an arp request packet ==== | ||
Here is an example of how to generate an arp request packet. | Here is an example of how to generate an arp request packet. | ||
Line 100: | Line 99: | ||
By entering " | By entering " | ||
+ | |||
+ | |||
+ | ==== Generating a null packet ==== | ||
+ | |||
+ | This option allows you to generate LLC null packets. | ||
+ | |||
+ | Remember that the size value (-s) defines the absolute size of an unencrypted packet, so you need to add 8 bytes to get its final length after encrypting it (4 bytes for iv+idx and 4 bytes for icv). This value also includes the 802.11 header with a length of 24bytes. | ||
+ | |||
+ | The command is: | ||
+ | |||
+ | | ||
+ | |||
+ | Where: | ||
+ | * --null means generate a LLC null packet (requires double dash). | ||
+ | * -s 42 specifies the packet length to be generated. | ||
+ | * -a BSSID is the MAC address of the access point. | ||
+ | * -h SMAC is the source MAC address of the packet to be generated. | ||
+ | * -w short-packet.cap is the name of the output file. | ||
+ | * -y fragment.xor is the name of the file containing the PRGA. | ||
+ | |||
+ | |||
+ | ==== Generating a custom packet ==== | ||
+ | If you want to generate a customer packet, first create a packet with the tool of your choice. | ||
+ | |||
+ | | ||
+ | |||
+ | Where: | ||
+ | * -9 means generate a custom packet. | ||
+ | * -r input.cap is the input file. | ||
+ | * -y keystream.xor is the file containing the PRGA. | ||
+ | * -w output.cap is the output file. | ||
+ | |||
+ | When it runs, packetforge-ng will ask you which packet to use and then output the file. | ||
Line 111: | Line 143: | ||
===== Usage Troubleshooting ===== | ===== Usage Troubleshooting ===== | ||
A common mistake people make is to include either or both -j and -o flags and create invalid packets. | A common mistake people make is to include either or both -j and -o flags and create invalid packets. | ||
- |
packetforge-ng.txt · Last modified: 2010/08/22 20:59 by mister_x