Differences

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

--- packetforge-ng [2007/01/27 18:31] – Added troubleshooting tip darkaudax
+++ packetforge-ng [2007/01/27 20:49] – Standardizing the format darkaudax
@@ Line 102: / Line 102: @@
-Usage Tip:
+===== Usage Tips =====
-   Most access points really don't care what IPs are used for the arp request.
+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 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
-Troubleshooting Tip:
+So the packetforge-ng command becomes:
-   A common mistake people make is to include either or both -j and -o flags and
+   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
-   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
+===== Usage Troubleshooting =====
-   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.