esnet/iperf

Mismatch between sent and received data size

Open

#382 建立於 2016年3月10日

在 GitHub 查看
 (5 留言) (2 反應) (0 負責人)C (4,946 star) (1,083 fork)batch import
Help Wantedbugbug:test-data

描述

I'm running iPerf 3.1.2 on 2 Ubuntu 14.04 machines.

If I run "iperf3 -c xx.xx.xx.xx -n 1M" because I only want to send around 1MB of data, on the receiver end, only around 350KB is received.

When I use wireshark to capture the packets, I can see that after around 350KB of data is received, the receiver (i.e., iperf server) sends a TCP RST to the sender and refuses to accept more data.

Is there some reason that iPerf behave this way? (maybe I missed something)

貢獻者指南

技術棧
c
領域
cliperformance
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
TCP basicsC programmingiperf usage
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
Investigate the implementation of the n flag in iperf3's source code, particularly in files like src/iperf api.c or src/iperf tcp.c. Examine the logic for when a TCP RST is sent after receiving data. Look for any related discussions in the comments on this issue for potential clues about the expected behavior or known limitations.
Mismatch between sent and received data size · esnet/iperf#382 | Good First Issue