Rafael, As Jaap said, this feature was just added to the project. I am in the process of creating the code to be able to have these fields in a column too. I think that would give you the functionality you are seeking.
Cheers, Sake On Thu, Sep 27, 2007 at 06:57:29AM +0200, Jaap Keuter wrote: > Hi, > > This feature was very recently added to the TCP dissector and is very > likely to be available in the next release. > > This is the commit record for the feature. > ------------------------------------------------------------------------ > r22966 | sake | 2007-09-25 22:37:13 +0200 (Tue, 25 Sep 2007) | 13 lines > > This patch adds two new fields to the tcp-dissector: > > tcp.time_relative ==> the time that has elapsed since the > first packet that was seen in the current TCP stream > > tcp.time_delta ==> the time that has elapsed since the > last packet that was seen in the current TCP stream > > Calculating these timestamps is turned off by default to not > use the extra memory that is needed for the per-packet-data. > It can be turned on through the TCP protocol preferences > > Thanx, > Jaap > > > [EMAIL PROTECTED] wrote: > > > > Hi all; > > Is there any way to display a time format like described below: > > Seconds since previous captured packet in the same TCP connection; > > > > Something like a generic Service Response Time. It would be great to > > help to locate THE problematic connection between all others. > > Thanks; > > Rafael Sarres de Almeida > > Se????o de Gerenciamento de Rede > > Superior Tribunal de Justi??a > > Tel: (61) 3319-9342 > > > > _______________________________________________ > Wireshark-users mailing list > Wireshark-users@wireshark.org > http://www.wireshark.org/mailman/listinfo/wireshark-users _______________________________________________ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
