Ask Wireshark - RSS feedhttps://ask.wireshark.org/questions/Wireshark questions and answersenCopyright Wireshark Foundation, 2017-2023Fri, 08 May 2020 09:13:53 +0000Statistics data-rate unitshttps://ask.wireshark.org/question/15709/statistics-data-rate-units/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!Thu, 09 Apr 2020 13:28:36 +0000https://ask.wireshark.org/question/15709/statistics-data-rate-units/Answer by currite for <p>Hi everyone, I'm new here.</p>
<p>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.</p>
<p>My believe is that the columns named <strong>Bits/s</strong> at tables <strong>Statistics -> Conversations</strong> and at <strong>Statistics -> Protocol Hierarchy</strong> do not measure <strong>Bits/s</strong> but a different data-rate unit, actually I believe they measure kilobit per second.</p>
<p>I believe <strong>Statistics -> I/O Graph</strong> gives the correct data-rate.</p>
<p>Values at <strong>I/O Graph</strong> are around 1000 times higher than those at <strong>Conversations</strong> and <strong>Protocol Hierarchy</strong>.</p>
<p>Can anyone have a look and let me know if I am right?</p>
<p>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.</p>
<p>Cheers!</p>
https://ask.wireshark.org/question/15709/statistics-data-rate-units/?answer=16503#post-id-16503Oops, 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 and sorry about that...Fri, 08 May 2020 09:13:53 +0000https://ask.wireshark.org/question/15709/statistics-data-rate-units/?answer=16503#post-id-16503Answer by cmaynard for <p>Hi everyone, I'm new here.</p>
<p>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.</p>
<p>My believe is that the columns named <strong>Bits/s</strong> at tables <strong>Statistics -> Conversations</strong> and at <strong>Statistics -> Protocol Hierarchy</strong> do not measure <strong>Bits/s</strong> but a different data-rate unit, actually I believe they measure kilobit per second.</p>
<p>I believe <strong>Statistics -> I/O Graph</strong> gives the correct data-rate.</p>
<p>Values at <strong>I/O Graph</strong> are around 1000 times higher than those at <strong>Conversations</strong> and <strong>Protocol Hierarchy</strong>.</p>
<p>Can anyone have a look and let me know if I am right?</p>
<p>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.</p>
<p>Cheers!</p>
https://ask.wireshark.org/question/15709/statistics-data-rate-units/?answer=15720#post-id-15720While 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.Thu, 09 Apr 2020 21:36:25 +0000https://ask.wireshark.org/question/15709/statistics-data-rate-units/?answer=15720#post-id-15720Comment by currite for <p>While both the <strong>Bits/s</strong> columns in the <strong>Statistics -> Conversations</strong> window, and the <strong>Bits/s</strong> column of the <strong>Statistics -> Protocol Hierarchy</strong> window suffer from rounding errors, they do in fact measure the average <strong>Bits/s</strong> of all the packets for the time duration of the capture file, as seen in the <strong>Statistics -> Capture File Properties</strong> window.</p>
<p>On the other hand, the <strong>Statistics -> I/O Graph</strong> plots <strong>Bits/s</strong> 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 <strong>not</strong> the same as an average for the entire duration.</p>
https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=16501#post-id-16501Oops, 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 !!Fri, 08 May 2020 09:12:52 +0000https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=16501#post-id-16501Comment by currite for <p>While both the <strong>Bits/s</strong> columns in the <strong>Statistics -> Conversations</strong> window, and the <strong>Bits/s</strong> column of the <strong>Statistics -> Protocol Hierarchy</strong> window suffer from rounding errors, they do in fact measure the average <strong>Bits/s</strong> of all the packets for the time duration of the capture file, as seen in the <strong>Statistics -> Capture File Properties</strong> window.</p>
<p>On the other hand, the <strong>Statistics -> I/O Graph</strong> plots <strong>Bits/s</strong> 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 <strong>not</strong> the same as an average for the entire duration.</p>
https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=16464#post-id-16464Hi 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.
Wed, 06 May 2020 23:23:07 +0000https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=16464#post-id-16464Comment by Chuckc for <p>While both the <strong>Bits/s</strong> columns in the <strong>Statistics -> Conversations</strong> window, and the <strong>Bits/s</strong> column of the <strong>Statistics -> Protocol Hierarchy</strong> window suffer from rounding errors, they do in fact measure the average <strong>Bits/s</strong> of all the packets for the time duration of the capture file, as seen in the <strong>Statistics -> Capture File Properties</strong> window.</p>
<p>On the other hand, the <strong>Statistics -> I/O Graph</strong> plots <strong>Bits/s</strong> 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 <strong>not</strong> the same as an average for the entire duration.</p>
https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=16465#post-id-16465What [language](https://ask.wireshark.org/question/16379/the-output-formats-in-wireshark-30x-and-wireshark-32x-for-decimals-differ/) is your system set for?Wed, 06 May 2020 23:47:13 +0000https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=16465#post-id-16465Comment by currite for <p>While both the <strong>Bits/s</strong> columns in the <strong>Statistics -> Conversations</strong> window, and the <strong>Bits/s</strong> column of the <strong>Statistics -> Protocol Hierarchy</strong> window suffer from rounding errors, they do in fact measure the average <strong>Bits/s</strong> of all the packets for the time duration of the capture file, as seen in the <strong>Statistics -> Capture File Properties</strong> window.</p>
<p>On the other hand, the <strong>Statistics -> I/O Graph</strong> plots <strong>Bits/s</strong> 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 <strong>not</strong> the same as an average for the entire duration.</p>
https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=15822#post-id-15822Hey, 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!
Tue, 14 Apr 2020 14:53:19 +0000https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=15822#post-id-15822Comment by cmaynard for <p>While both the <strong>Bits/s</strong> columns in the <strong>Statistics -> Conversations</strong> window, and the <strong>Bits/s</strong> column of the <strong>Statistics -> Protocol Hierarchy</strong> window suffer from rounding errors, they do in fact measure the average <strong>Bits/s</strong> of all the packets for the time duration of the capture file, as seen in the <strong>Statistics -> Capture File Properties</strong> window.</p>
<p>On the other hand, the <strong>Statistics -> I/O Graph</strong> plots <strong>Bits/s</strong> 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 <strong>not</strong> the same as an average for the entire duration.</p>
https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=15744#post-id-15744I'm not sure why some folks are encountering the *"Internal Server Error"* message, for example:
- [Help! Asking a question causes Internal Server Error.](https://ask.wireshark.org/question/15559/help-asking-a-question-causes-internal-server-error/)
- [Bug 16480 - Asking a question returns Internal Server error.](https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16480)
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.Fri, 10 Apr 2020 18:27:13 +0000https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=15744#post-id-15744Comment by Chuckc for <p>While both the <strong>Bits/s</strong> columns in the <strong>Statistics -> Conversations</strong> window, and the <strong>Bits/s</strong> column of the <strong>Statistics -> Protocol Hierarchy</strong> window suffer from rounding errors, they do in fact measure the average <strong>Bits/s</strong> of all the packets for the time duration of the capture file, as seen in the <strong>Statistics -> Capture File Properties</strong> window.</p>
<p>On the other hand, the <strong>Statistics -> I/O Graph</strong> plots <strong>Bits/s</strong> 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 <strong>not</strong> the same as an average for the entire duration.</p>
https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=15742#post-id-15742Fixed (language setting on machine): https://www.wireshark.org/lists/wireshark-users/202004/msg00004.htmlFri, 10 Apr 2020 17:35:24 +0000https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=15742#post-id-15742Comment by Chuckc for <p>While both the <strong>Bits/s</strong> columns in the <strong>Statistics -> Conversations</strong> window, and the <strong>Bits/s</strong> column of the <strong>Statistics -> Protocol Hierarchy</strong> window suffer from rounding errors, they do in fact measure the average <strong>Bits/s</strong> of all the packets for the time duration of the capture file, as seen in the <strong>Statistics -> Capture File Properties</strong> window.</p>
<p>On the other hand, the <strong>Statistics -> I/O Graph</strong> plots <strong>Bits/s</strong> 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 <strong>not</strong> the same as an average for the entire duration.</p>
https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=15723#post-id-15723https://wiki.wireshark.org/SampleCaptures<br>
[http_with_jpegs.cap.gz](https://wiki.wireshark.org/SampleCaptures?action=AttachFile&do=get&target=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.<br>
I wonder if the "k" is not being displayed properly. The capture above has several conversations of different speeds.<br>
[Screen shot from man page](https://www.wireshark.org/docs/wsug_html_chunked/ChStatConversations.html) for discussion.Fri, 10 Apr 2020 00:06:22 +0000https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=15723#post-id-15723Comment by cmaynard for <p>While both the <strong>Bits/s</strong> columns in the <strong>Statistics -> Conversations</strong> window, and the <strong>Bits/s</strong> column of the <strong>Statistics -> Protocol Hierarchy</strong> window suffer from rounding errors, they do in fact measure the average <strong>Bits/s</strong> of all the packets for the time duration of the capture file, as seen in the <strong>Statistics -> Capture File Properties</strong> window.</p>
<p>On the other hand, the <strong>Statistics -> I/O Graph</strong> plots <strong>Bits/s</strong> 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 <strong>not</strong> the same as an average for the entire duration.</p>
https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=15722#post-id-15722Perhaps if you provide a [small] capture file that, so we can all refer to the same concrete example?Thu, 09 Apr 2020 23:19:47 +0000https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=15722#post-id-15722Comment by currite for <p>While both the <strong>Bits/s</strong> columns in the <strong>Statistics -> Conversations</strong> window, and the <strong>Bits/s</strong> column of the <strong>Statistics -> Protocol Hierarchy</strong> window suffer from rounding errors, they do in fact measure the average <strong>Bits/s</strong> of all the packets for the time duration of the capture file, as seen in the <strong>Statistics -> Capture File Properties</strong> window.</p>
<p>On the other hand, the <strong>Statistics -> I/O Graph</strong> plots <strong>Bits/s</strong> 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 <strong>not</strong> the same as an average for the entire duration.</p>
https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=15721#post-id-15721Hi 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?Thu, 09 Apr 2020 22:50:12 +0000https://ask.wireshark.org/question/15709/statistics-data-rate-units/?comment=15721#post-id-15721