Statistics data-rate units

asked 2020-04-09 13:28:36 +0000

currite
1 ●1 ●3

updated 2020-04-09 13:43:52 +0000

Hi everyone, I'm new here.

I am measuring data rates using Wireshark 3.2.2 and I believe some of the data-rate units at "Statistics" 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 and at 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.

Cheers!

edit retag flag offensive close merge delete

add a comment

answered 2020-04-09 21:36:25 +0000

cmaynard

11115 ●11 ●317 ●165 https://www.igt.com/

While both the Bits/s columns in the Statistics -> Conversations window, and the Bits/s column of the Statistics -> Protocol Hierarchy window suffer from rounding errors, they do in fact measure the average Bits/s of all the packets for the time duration of the capture file, as seen in the Statistics -> Capture File Properties window.

On the other hand, the Statistics -> I/O Graph plots Bits/s averaged over whatever the chosen plotting time interval is that's selected. By default, the interval is "1 sec"; therefore, for every second of time that has elapsed in the capture file, the graph is displaying the average value for that particular 1 second interval, and that is repeated for every such interval. This is not the same as an average for the entire duration.

edit flag offensive delete link

Comments

Hi cmaynard. Thank you very much for your answer, I see that difference, but I think that is not the problem. I still do not know the reason why I/O Graph shows me the rate I expect while Conversations and Protocol Hierarchy show me a value 1000 times lower than expected. That's why I thought maybe Conversations and Protocol Hierarchy data-rate columns should read in their tittle kilobit/s instead of Bit/s. Did you test it?

currite ( 2020-04-09 22:50:12 +0000 )edit

Perhaps if you provide a [small] capture file that, so we can all refer to the same concrete example?

cmaynard ( 2020-04-09 23:19:47 +0000 )edit

https://wiki.wireshark.org/SampleCapt...
http_with_jpegs.cap.gz http_with_jpegs.cap.gz A simple capture containing a few JPEG pictures one can reassemble and save to a file.
I wonder if the "k" is not being displayed properly. The capture above has several conversations of different speeds.
Screen shot from man page for discussion.

Chuckc ( 2020-04-10 00:06:22 +0000 )edit

Fixed (language setting on machine): https://www.wireshark.org/lists/wires...

Chuckc ( 2020-04-10 17:35:24 +0000 )edit

I'm not sure why some folks are encountering the "Internal Server Error" message, for example:

Someone with more access than I have will likely need to enable debug on the site in order to help get to the bottom of this problem.

cmaynard ( 2020-04-10 18:27:13 +0000 )edit

Hey, sorry for my late reply, I tried to post days before, but apparently I was being banned by Askbot because I was using the word "spa". But now I have been told that's been fixed.

So, I was just trying to say that it was my fault, a stupid thing I did.

My computer was in Spanish, so number 1.004 actually meant one thousand and four!! - you know this bad standard thing of writing numbers differently depending on the language you are in...

Thank you cmaynard for your answers.

Cheers!

currite ( 2020-04-14 14:53:19 +0000 )edit

Hi again @cmaynard, @bubbasnmp and whoever reads this.

I thought it was my fault, a problem with the language of my computer, but, after some more tests, now I don't think that was the problem, now I think again the problem is on Wireshark.

Please have a look at this image https://imagebin.ca/v/5LdRt1y2KvFK

The marked figures have a dot, not a comma. They are not properly indicating the right units, they are missing a k (for thousand). I measured it.

Please test it yourself. And, if you agree there is a problem there, please let me know what the next step is. I can open a Pull Request if needed.

currite ( 2020-05-06 23:23:07 +0000 )edit

What language is your system set for?

Chuckc ( 2020-05-06 23:47:13 +0000 )edit

Oops, it was in Spanish! So forget about it. I guess everything is ok.

Very sad non having a universally standard way of writing numbers.

Thank you @bubbasnmp !!

currite ( 2020-05-08 09:12:52 +0000 )edit

add a comment

Statistics data-rate units

1 Answer

Comments

Your Answer

Question Tools

Stats

Related questions

Statistics data-rate units edit

1 Answer

Comments

Your Answer

Question Tools

Stats

Related questions

Statistics data-rate units