Repository navigation
iperf3 UDP sender limited to ~10 Mbps over Ethernet but ~95 Mbps over Wi-Fi #2070
|
Hello, I'm trying to understand a strange iperf3 UDP issue on Ubuntu/Linux that only appears during upload:
The strange part is that the Ethernet test itself only generates around 10–12 Mbps, while the Wi-Fi-sourced test can generate around 95 Mbps. I'd like to understand the actual root cause of this behavior. I’m happy to provide any additional logs, command outputs, traces, or run any tests that may help diagnose the issue. |
Replies: 4 comments 5 replies
|
Check the link speed first: ethtool <iface> | grep -E 'Speed|Duplex|Auto-negotiation'I'd expect The Wi-Fi path isn't fast, it's normal. The Ethernet one is degraded. And your finding that affinity, pacing and qdisc changed nothing is the giveaway, none of those can get you past what the PHY negotiated. Two checks: iperf3 -c <server> -t 10TCP around 9.4 Mbps confirms it, that's 10BASE-T minus framing, and rules out anything UDP specific. dmesg | grep -i 'link is up'Prints the negotiated speed from when the link came up. If it is 10 Mbps: usually a damaged cable with only two good pairs (100BASE-TX needs two, gigabit needs four, so a partly broken cable degrades instead of failing), a bad switch port, or autoneg forced somewhere. Swap the cable first. If ethtool says 1000Mb/s full duplex then it's a real iperf3 question, post the output. |
|
Hi, can you add some details?
|
The screenshot you included shows a TCP test, not UDP. Can it be that somehow you forgot the If this is not the case, can you include a similar screenshot for the UDP test (without the |
|
Hi, thanks for the added information. I now believe that the UDP sending rate limitation is because of the Ethernet flow control. The SIP Router does not allow the computer to send over 10Mbps, so its network buffers gets full. This is also indicated by the over 3 seconds jitter (vs 0.35 sec in the downlink). I don't have an explanation for the rate growth over time. Maybe the ISP implements some compression algorithm that learns over time. To test, try to disable the Ethernet flow control. Another option may be to connect the Ethernet from the client computer to a second router that is connected to the ISP Router over LAN (or WiFi). In this case the second router will not have the 10Mbps limit so the flow control will not be activated (at least not below the LAN/WiFi throughput). |



Hi, thanks for the added information. I now believe that the UDP sending rate limitation is because of the Ethernet flow control. The SIP Router does not allow the computer to send over 10Mbps, so its network buffers gets full. This is also indicated by the over 3 seconds jitter (vs 0.35 sec in the downlink). I don't have an explanation for the rate growth over time. Maybe the ISP implements some compression algorithm that learns over time.
To test, try to disable the Ethernet flow control. Another option may be to connect the Ethernet from the client computer to a second router that is connected to the ISP Router over LAN (or WiFi). In this case the second router will not have the 10Mbps…