packetforge-ng
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
packetforge-ng [2007/04/27 16:58] – added examples for v.8 new features darkaudax | packetforge-ng [2009/01/23 22:01] – Fixed typo. darkaudax | ||
---|---|---|---|
Line 20: | Line 20: | ||
*-e : disables WEP encryption | *-e : disables WEP encryption | ||
*-k < | *-k < | ||
- | *-l < | + | *-l < |
*-t ttl : set Time To Live | *-t ttl : set Time To Live | ||
*-w < | *-w < | ||
Line 132: | Line 132: | ||
When it runs, packetforge-ng will ask you which packet to use and then output the file. | When it runs, packetforge-ng will ask you which packet to use and then output the file. | ||
+ | |||
Line 139: | Line 140: | ||
So the packetforge-ng command becomes: | So the packetforge-ng command becomes: | ||
- | | + | |
===== Usage Troubleshooting ===== | ===== Usage Troubleshooting ===== | ||
+ | |||
+ | ==== Including both -j and -o flags ==== | ||
+ | |||
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. | ||
+ | |||
+ | |||
+ | ==== Error message "Mode already specified" | ||
+ | |||
+ | This is commonly caused by using the number one (-1) instead of dash lowercase L (-l) in the command. | ||
+ | |||
+ | Entering: | ||
+ | | ||
+ | |||
+ | Gives: | ||
+ | Mode already specified. | ||
+ | " | ||
+ | |||
+ | This because -1 was used instead of the correct -l. So simply use " | ||
+ |
packetforge-ng.txt · Last modified: 2010/08/22 20:59 by mister_x