Package: ethereal-common
Version: 0.10.10-2
Severity: wishlist

Two things that caused a lot of grief here:

1. The manpage says "Text2pcap understands a hexdump of the form
generated by od -t x1". While this is not really wrong, it is still
misleading since od (at least in Debian sarge) defaults the offsets to
octal while text2pcap assumes hex. Therefore text2pcap parses only the
first 16 bytes of a dump created by the od usage printed above (and
prepends a 28 bytes header, see below). Please change that sentence to
"(...) generated by od -Ax -t x1" to match the sample output given in
the following lines.

2. (unresolved) In order to understand the functionality of text2pcap
I'd like to do a full binary -> hexdump -> binary conversion loop.
However, after an
$ od -Ax -t x1 sample.pcap >sample.txt
$ text2pcap sample.txt sample.pcap.again
using an arbitrary pcap file I find a resulting pcap file 40 bytes
longer than the original one. Appearently text2pcap tried to frame the
input thus destroying the original frame and packet order within, which
is not what I want, at least not here. The manpage reads as text2pcap's
default behaviour was to simply convert the hex dump to a binary file
without further manipulation. How could this be achieved?

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.11.8
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages ethereal-common depends on:
ii  libc6                       2.3.2.ds1-21 GNU C Library: Shared libraries an
ii  libglib1.2                  1.2.10-9     The GLib library of C routines
ii  zlib1g                      1:1.2.2-4    compression library - runtime


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to