FYI: From the discussions on this group, I have added two bugs to the
database regarding File->Import and text2pcap. A quick summary:
Bug #1628: Add an enhancement to Wireshark for File->Import.
Bug #1636: Correct text2pcap's handling of exported capture files that
include packet summary and/or details information, and make use of the
timestamps, if they're available.
(Bug #1628 has a dependency on Bug #1636.)
BTW: Who determines the priority and severity of bugs? For now, I
marked them both as low priority and the 1st one as an Enhancement and
the second one as Minor.
From: [email protected]
[mailto:[email protected]] On Behalf Of Sake Blok
Sent: Thursday, May 31, 2007 4:34 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] File:Import?
On Wed, May 30, 2007 at 04:06:16PM -0400, Maynard, Chris wrote:
> Anyway, I can open a bug for an enhancement to add "File -> Import".
> But it seems that there should also be a separate bug report on
> text2pcap to be able to deal with the packet summary details and to be
> able to glean the timestamp information from the file, if it's
> available. Would you agree?
In my opinion it would be great to have the "text2pcap" functionality
available from within wireshark as "File | Import". Also nice would
be if a text file was just another type of capture file wireshark
can read. That way, tshark can also handle text files and there would
be no need to seperately maintain the "Import" code and the "text2pcap"
code (wihtout losing the ability to convert text files to pcap files
on from the cli).
Another nice feature on top of this would be to be able to read
"NetScreen" snoop dumps without first having to convert them with
So, yes, I would vote for a "bug for enhancement" :-)
(also for your other enhancements concerning packet summary details
and reading the timestamps)
Wireshark-dev mailing list
This email may contain confidential and privileged material for the
sole use of the intended recipient(s). Any review, use, retention,
distribution or disclosure by others is strictly prohibited. If you
are not the intended recipient (or authorized to receive for the
recipient), please contact the sender by reply email and delete all
copies of this message. Also, email is susceptible to data
corruption, interception, tampering, unauthorized amendment and
viruses. We only send and receive emails on the basis that we are
not liable for any such corruption, interception, tampering,
amendment or viruses or any consequence thereof.