Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: Re: [Wireshark-users] Statistics data-rate units

From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Sun, 12 Apr 2020 18:40:30 -0700
Askbot (the software that runs ask.wireshark.org) has a banned word list as part of its moderation feature. The word "spa" was in the list, which was matching the word "Spanish" in your message. I removed the offending entry, so you should be able to post now.

On 4/10/20 9:50 AM, sll wrote:
> Hey, it was my fault, it was just a stupid thing of mine!
> 
> My computer was in Spanish and average number 1.004 actually meant one
> thousand and four!!
> 
> You know this bad thing of writing numbers differently depending on the
> language you are in...
> 
> I'm trying to say this at ask.wireshark.org, but I always get "Internal
> Server Error" when sending my message...
> 
> 
> Cheers
> 
> sll:
>> Ah, ok. I'll ask there. Thank you Chuck!
>>
>> On 9/4/20 14:55, chuck c wrote:
>>> You'll probably get more eyeballs looking at it on the Q&A site:
>>> https://ask.wireshark.org/questions/
>>>
>>> On Thu, Apr 9, 2020 at 7:32 AM sll <sll@xxxxxxxxxxx
>>> <mailto:sll@xxxxxxxxxxx>> wrote:
>>>
>>>     Hi everyone, I'm new to the list.
>>>
>>>     I am measuring data rates using Wireshark 3.2.2 and I believe some of
>>>     the data-rate units at "Statitstics" are non-consistent with my
>>>     tests. I
>>>     am not 100% sure, I might be missing something, so I would like
>>>     someone
>>>     else to have a look.
>>>
>>>     My believe is that the columns named "Bits/s" at tables
>>>     Statistics -> Conversations
>>>     Statistics -> Protocol Hierarchy
>>>     do not measure Bits/s but a different data-rate unit, actually I
>>>     believe
>>>     they measure kilobit per second.
>>>
>>>     I believe
>>>     Statistics -> I/O Graph
>>>     gives the correct data-rate.
>>>
>>>     Values at I/O Graph are around 1000 times higher than those at
>>>     Conversations and Protocol Hierarchy.
>>>
>>>     Can anyone have a look and let me know if I am right?
>>>
>>>     If I am, where can I ask to fix it? I am not a developer but I'd be
>>>     happy to open an issue or whatever is needed.
>>>
>>>     Please let me know if you think this question should go to a
>>>     different
>>>     Wireshark list and I will subscribe to it to ask my question.
>>>
>>>     Cheers!
>>>
>>>    
>>> ___________________________________________________________________________
>>>
>>>     Sent via:    Wireshark-users mailing list
>>>     <wireshark-users@xxxxxxxxxxxxx
>>> <mailto:wireshark-users@xxxxxxxxxxxxx>>
>>>     Archives: https://www.wireshark.org/lists/wireshark-users
>>>     Unsubscribe:
>>> https://www.wireshark.org/mailman/options/wireshark-users
>>>                  mailto:wireshark-users-request@xxxxxxxxxxxxx
>>>     <mailto:wireshark-users-request@xxxxxxxxxxxxx>?subject=unsubscribe
>>>
>>>
>>> ___________________________________________________________________________
>>>
>>> Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
>>> Archives:    https://www.wireshark.org/lists/wireshark-users
>>> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
>>>              
>>> mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
>>
>>
>> ___________________________________________________________________________
>> Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
>> Archives:    https://www.wireshark.org/lists/wireshark-users
>> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
>>              mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
>>
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives:    https://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
>              mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
>