ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 1849] tshark conversation output does not include start da

Date: Sun, 15 Jul 2012 12:14:38 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1849

Guy Harris <guy@xxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |
            Summary|tshark conversation output  |tshark conversation output
                   |does not include date/time  |does not include start
                   |information                 |date/time for the
                   |                            |conversation
         OS/Version|Linux (other)               |All

--- Comment #3 from Guy Harris <guy@xxxxxxxxxxxx> 2012-07-15 12:14:38 PDT ---
I don't think that's what he meant.

From

> It would be ideal for my usage if a date & time could be printed, probably via an optional switch, of the start of the socket pair for TCP or the first packet seen for UDP.

it sounds as if he wants, for each conversation in the "-z conv,{tcp,udp}"
output, a time stamp of the first packet (or, for TCP, perhaps the final
SYN+ACK - he doesn't indicate what "the start of the socket pair" means; is it
the initial SYN or the final SYN+ACK?).  That's not currently produced.

The Wireshark conversation taps give a lot more columns, including a column
giving the time stamp, relative to the first packet in the capture, of the
first packet in the conversation.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.