Is there a plan to update the I/O graph to include a similar advanced options which allows for min/max/avg. Current graphing of things like bytes in flight are not accurate forcing the use of version 1 Wireshark.

Comparing receive window to bytes in flight helps to understand how well a sender keeps the network as full of packet as possible. The old version of Wireshark with advanced options allows for that comparison accurately. Current versions >2.0 appears to graph max values which does not show the real gap between the two metrics.

As Wireshark development goes, implementing missing features or fixing unexpected/wrong behavior is not planned unless there's a bug report/enhancement request for it at https://bugs.wireshark.org.

So if you want to have Wireshark improved (and can't submit a patch yourself), please open a bug or enhancement request at the bug tracker. The more details you can give (screenshots, pcap files, etc) to help the developers understand the problem/the improvement the more likely it is that one of them picks up the bug and implements a change.

24.1k

Jasper

answered 2019-03-23 10:44:50 +0000

edit flag offensive 0 remove flag delete link

Comments

add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Is there a plan to update the I/O graph to include a similar advanced options which allows for min/max/avg. Current graphing of things like bytes in flight are not accurate forcing the use of version 1 Wireshark. edit

Comments

1 Answer

Comments