https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16796
--- Comment #5 from Christopher Maynard <christopher.mayn...@igt.com> ---
(In reply to Jaap Keuter from comment #4)
> In the Endpoint statistics it's counting packets _per endpoint_. Naturally a
> packet egressing an endpoint will ingress another (the whole point of
> networking). The endpoint statistics are meant to reflect that, in their Rx
> and Tx counts, which culminates in total packets per interface. So yes, a
> packet egressing an interface will ingress one at the other end of the path.
>
> The count of packets _in the network_ is found in the Conversations
> statistics. There the path between endpoints is listed and the packets
> exchanged on that path, both in the forward and backward direction.
>
> I think both statistics come into their own, providing a different view to
> the same packet flow.
There are 2 packets in the capture file. Any number higher than 2 in the
"Packets" column can't possibly be correct. The question the "Packets" column
answers is, "Of the 2 total packets in the capture file, how many of them did
this particular endpoint either send or receive?" The answer is 2. If you
provide an answer of 4, then you're not counting packets, you're counting
something else. I suppose you're counting "Instances of an Endpoint occurring
as either the transmitter or the receiver of a packet", but then the column
name should be changed from "Packets" to "Instances of an Endpoint occurring as
either the transmitter or the receiver of a packet" in order for the value of 4
to make any sense. I'd prefer Wireshark simply not duplicate the packets and
bytes counting as it's doing now rather than change the column names to reflect
what it is doing now.
--
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
