Re: about wireshark SRT statistics confusion

[ronnie sahlberg <ronniesahlberg () gmail com>]

That looks like a bug in the Diameter protocol SRT.

Most likely it can not handle if the transaction id is "reused" so it
ends up matching a reply from one transaction with a request that
happened for a different transaction much later.


Do you have an example trace where this happens ?
If so I can fix that issue.


regards
ronnie sahlberg


On Wed, Jun 2, 2010 at 12:47 PM, Bo Xu <xubo.leo () gmail com> wrote:
> Hello Guys ,
>
>   SRT statistic is a really fantastic function of Wireshark .  I am doing
> the Diameter SRT.  But the Output is really confusion
>
>   For this pcap file <nocaaa.tcpdump.201006021007.pcap> , i got such result
> :
> index    procedure         calls       MinSRT              MaxSRT     AvgSRT
> 1          Credit-control    3132       -123.-68142        0.17384
> 58897650236.50013
>
> It looks very strange about MinSRT/AvgSRT value , and btw : the unit is
> second ?
> My Wireshark version is :Version 1.2.8 (SVN Rev 32676)
>
> BR
> Xu Bo
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
> Archives:    http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>             mailto:wireshark-users-request () wireshark org?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe