Re: Statistics data-rate units

[sll <sll () disroot org>]

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 () disroot org
> > <mailto:sll () disroot org>> 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 () wireshark org
> > <mailto:wireshark-users () wireshark org>>
> >     Archives: https://www.wireshark.org/lists/wireshark-users
> >     Unsubscribe:
> > https://www.wireshark.org/mailman/options/wireshark-users
> >                  mailto:wireshark-users-request () wireshark org
> >     <mailto:wireshark-users-request () wireshark org>?subject=unsubscribe
> >
> >
> > ___________________________________________________________________________
> >
> > Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
> > Archives:    https://www.wireshark.org/lists/wireshark-users
> > Unsubscribe: https://www.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:    https://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://www.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:    https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe