forked from osmocom/wireshark
Text2Pcap docs update
Minor update to docs Change-Id: If9464f00d69bb9a8bb5638f3bb0d0f73a56aad50 Reviewed-on: https://code.wireshark.org/review/16856 Reviewed-by: Graham Bloice <graham.bloice@trihedral.com>
This commit is contained in:
parent
0d5cf54483
commit
472f789b73
|
@ -37,11 +37,13 @@ processable packet dumps from hexdumps of application-level data only.
|
|||
|
||||
B<Text2pcap> understands a hexdump of the form generated by I<od -Ax
|
||||
-tx1 -v>. In other words, each byte is individually displayed, with
|
||||
spaces separating the bytes from each other. Each line begins with an
|
||||
offset describing the position in the file, with a space separating it
|
||||
from the following bytes. 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:
|
||||
spaces separating the bytes from each other. Each line begins with an offset
|
||||
describing the position in the packet, each new packet starts with an offset
|
||||
of 0 and there is a space separating the offset from the following bytes.
|
||||
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 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
|
||||
|
|
Loading…
Reference in New Issue