aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorChris Maynard <Christopher.Maynard@GTECH.COM>2013-12-26 03:45:12 +0000
committerChris Maynard <Christopher.Maynard@GTECH.COM>2013-12-26 03:45:12 +0000
commit841156804816e5a00087f3a82e7c3e47335bffab (patch)
tree12deead7d35de4c4efa0d766e31364e8efc36934 /doc
parentc0823e1977240ba2ee01606bbf764a1d64a2682d (diff)
Since the documentation states that, "Text2pcap understands a hexdump of the form generated by od -Ax -tx1 -v.", supply an example that actually matches that format.
In addition, change the hex bytes so that they represent a valid, well-formed packet, rather than a malformed RSVP packet. This should allow a user to more clearly verify that the text2pcap converstion worked as expected in the event he/she desires to test text2pcap using the example provided. svn path=/trunk/; revision=54454
Diffstat (limited to 'doc')
-rw-r--r--doc/text2pcap.pod12
1 files changed, 5 insertions, 7 deletions
diff --git a/doc/text2pcap.pod b/doc/text2pcap.pod
index 983a7acd6d..30981131ee 100644
--- a/doc/text2pcap.pod
+++ b/doc/text2pcap.pod
@@ -41,13 +41,11 @@ the position in the file. The offset is a hex number (can also be
octal or decimal - see B<-o>), of more than two hex digits.
Here is a sample dump that B<text2pcap> can recognize:
- 000000 00 e0 1e a7 05 6f 00 10 ........
- 000008 5a a0 b9 12 08 00 46 00 ........
- 000010 03 68 00 00 00 00 0a 2e ........
- 000018 ee 33 0f 19 08 7f 0f 19 ........
- 000020 03 80 94 04 00 00 10 01 ........
- 000028 16 a2 0a 00 03 50 00 0c ........
- 000030 01 01 0f 19 03 80 11 01 ........
+ 000000 00 0e b6 00 00 02 00 0e b6 00 00 01 08 00 45 00
+ 000010 00 28 00 00 00 00 ff 01 37 d1 c0 00 02 01 c0 00
+ 000020 02 02 08 00 a6 2f 00 01 00 01 48 65 6c 6c 6f 20
+ 000030 57 6f 72 6c 64 21
+ 000036
There is no limit on the width or number of bytes per line. Also the
text dump at the end of the line is ignored. Bytes/hex numbers can be