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.