aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorChris Maynard <Christopher.Maynard@GTECH.COM>2013-09-09 01:04:13 +0000
committerChris Maynard <Christopher.Maynard@GTECH.COM>2013-09-09 01:04:13 +0000
commiteeba21136c3ed0f45e8a17b5daa422cd8c008c38 (patch)
tree072b48fd33eea2411d525c2d672f2be25ebc3413 /doc
parentbffe25fdc22c076cca8bb5b48aac4e80d5fbd730 (diff)
OK, allow either positive or negative offsets no matter if we're chopping from the beginning or the end.
Given the following example, it's now possible to chop the 10 bytes depicted from the 100 byte packet 4 different ways and achieve the exact same results: <-------- 100 --------> Methods: 1) editcap -C 20:10 in.pcap out.pcap +------+----+---------+ 2) editcap -C -80:10 in.pcap out.pcap | 20 | 10 | 70 | 3) editcap -C -70:-10 in.pcap out.pcap +------+----+---------+ 4) editcap -C 30:-10 in.pcap out.pcap svn path=/trunk/; revision=51854
Diffstat (limited to 'doc')
-rw-r--r--doc/editcap.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/editcap.pod b/doc/editcap.pod
index 00422e4bcd..fda1228558 100644
--- a/doc/editcap.pod
+++ b/doc/editcap.pod
@@ -96,8 +96,8 @@ chopped by <choplen> bytes of data. Positive values chop at the packet
beginning while negative values chop at the packet end.
If an optional offset precedes the <choplen>, then the bytes chopped will be
-offset from that value. Offsets are expected to be positive values, regardless
-of chopping from packet beginning or packet end.
+offset from that value. Positve offsets are from the packet beginning, while
+negative offsets are from the packet end.
This is useful for chopping headers for decapsulation of an entire capture,
removing tunneling headers, or in the rare case that the conversion between two