IPerf3 shows inaccurate numbers on Transfer Bytes (comparing with wireshark)

[mzazure]

see below screenshot. Can someone help explain this?

[davidBar-On]

By default, Wireshark calculates the SEQ per the packets it captures. Therefore, when not all packets are captured, SEQ will not be the actual number. See this StackExchange explanation, including how to view the real SEQ number.

In this case, as there are 240ms between packets 14 and 19, probably Wireshark did not capture many of the packets during this period of time.

[mzazure]

Thanks for the clarification! I realized that the numbers are aligned when the payload is big