Differences

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

--- packetforge-ng [2007/01/26 23:44] – cosmetic changes mister_x
+++ packetforge-ng [2007/01/27 20:49] – Standardizing the format darkaudax
@@ Line 37: / Line 37: @@
       *--icmp         : forge an ICMP packet   (-2)
       *--custom       : build a custom packet  (-9)
 ===== Usage Example =====
@@ Line 52: / Line 54: @@
   *-a 00:14:6C:7E:40:80 is the Access Point MAC address
   *-h 00:0F:B5:AB:CB:9D is the source MAC address you wish to use
-  *-k 255.255.255.255 is the destination IP.  IE In an arp it is the "Who has this IP"
+  *-k 192.168.1.100 is the destination IP.  IE In an arp it is the "Who has this IP"
-  *-l 255.255.255.255 is the source IP.  IE In an arp is the "Tells this IP"
+  *-l 192.168.1.1 is the source IP.  IE In an arp it is the "Tell this IP"
   *-y fragment-0124-161129.xor
   *-w arp-packet
@@ Line 95: / Line 97: @@
   Saving chosen packet in replay_src-0124-163529.cap
   You should also start airodump-ng to capture replies.
+  End of file.
-End of file.
 By entering "y" above, the packet you created with packetforge-ng is then injected.
+===== Usage Tips =====
+Most access points really don't care what IPs are used for the arp request.  So as a result you can use 255.255.255.255 for source and destination IPs.
+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.1 -y fragment-0124-161129.xor -w arp-request
+===== Usage Troubleshooting =====
+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.