https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14604
Michael Mann <mman...@netscape.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS|Windows 10 |All
Component|Common utilities |Dissection engine
|(libwsutil) |(libwireshark)
Hardware|x86-64 |All
CC| |mman...@netscape.net
Status|INCOMPLETE |CONFIRMED
--- Comment #3 from Michael Mann <mman...@netscape.net> ---
I think this is a "documentation" issue more than a bug. The AvgBW is
calculated on the whole stream, but MaxBW is only calculated in a sliding
window (not sure why). I can manipulate the Burst measurement interval and
that will effect the MaxBW (and depending on the capture, it can be > AvgBW).
I can trace the calculations in the code, but don't understand the meaning.
"Sliding window" means something to me for TCP, but I don't see how it's
applied to UDP.
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe