User Tools

Site Tools


packetforge-ng

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
packetforge-ng [2007/04/27 16:58] – added examples for v.8 new features darkaudaxpacketforge-ng [2009/01/23 22:01] – Fixed typo. darkaudax
Line 20: Line 20:
       *-e             : disables WEP encryption       *-e             : disables WEP encryption
       *-k <ip[:port]> : set Destination IP [Port]       *-k <ip[:port]> : set Destination IP [Port]
-      *-l <ip[:port]> : set Source      IP [Port]+      *-l <ip[:port]> : set Source      IP [Port] (Dash lowercase letter L)
       *-t ttl         : set Time To Live       *-t ttl         : set Time To Live
       *-w <file>      : write packet to this pcap file       *-w <file>      : write packet to this pcap file
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:
-   packetforge-ng -0 -a 00:14:6C:7E:40:80 -h 00:0F:B5:AB:CB:9D -k 192.168.1.100 -l 192.168.1.-y fragment-0124-161129.xor -w arp-request+   packetforge-ng -0 -a 00:14:6C:7E:40:80 -h 00:0F:B5:AB:CB:9D -k 255.255.255.255 -l 255.255.255.255 -y fragment-0124-161129.xor -w arp-request 
  
 ===== 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.  These flags adjust the FromDS and ToDS flages in the packet generated.  Unless you are doing something special and really know what you are doing, don't use them.  In general, they are not needed. A common mistake people make is to include either or both -j and -o flags and create invalid packets.  These flags adjust the FromDS and ToDS flages in the packet generated.  Unless you are doing something special and really know what you are doing, don't use them.  In general, they are not needed.
 +
 +
 +==== 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:
 +   packetforge-ng -0 -a 00:14:6C:7E:40:80 -h 00:09:5B:EC:EE:F2 -k 255.255.255.255 -1 255.255.255.255 -y 00:14:6C:7E:40:80-03-00-14-6C-7E-40-80.xor -w arp-request 
 +
 +Gives:
 +   Mode already specified.
 +   "packetforge-ng --help" for help.
 +
 +This because -1 was used instead of the correct -l.  So simply use "-l".
 +
packetforge-ng.txt · Last modified: 2010/08/22 20:59 by mister_x