Ask Your Question
0

Statistics data-rate units

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

currite gravatar image

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

1 Answer

Sort by ยป oldest newest most voted
0

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

cmaynard gravatar image

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 more

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 gravatar imagecurrite ( 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 gravatar imagecmaynard ( 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 gravatar imageChuckc ( 2020-04-10 00:06:22 +0000 )edit

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

Chuckc gravatar imageChuckc ( 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 gravatar imagecmaynard ( 2020-04-10 18:27:13 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

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

Seen: 98 times

Last updated: Apr 09