Bug 1910200 - Client issues WARNING: did not receive ack of last datagram
Summary: Client issues WARNING: did not receive ack of last datagram
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: iperf
Version: 33
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Steven Roberts
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-23 05:14 UTC by gnemas
Modified: 2021-01-02 01:08 UTC (History)
3 users (show)

Fixed In Version: iperf-2.0.13-6.fc33
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-02 01:08:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description gnemas 2020-12-23 05:14:15 UTC
Description of problem:

Client hangs when using default UDP client and server settings. This does not appear to be an upstream issue because if I build the package myself, this does not happen.

Version-Release number of selected component (if applicable):

iperf-2.0.13-5.fc33.x86_64


How reproducible: always


Steps to Reproduce:
1. Start server using the command "iperf -s -u"
2. Start client using the command "iperf -c 127.0.0.1 -u"
3. Wait approximately 12 seconds

Actual results:

The client issues the warning "WARNING: did not receive ack of last datagram after 10 tries" and hangs until Ctrl-C is pressed.

Expected results:

The client should terminate normally with expected packet statistics.

Additional info:

This behavior is not seen if I build iperf myself from the same source package referenced in the spec file. This also was not seen in the f32 version, so it seems to have something to do with the way this package was built. I suspect it has to do with the size of signed integers, since a negative value is what the client uses to request the server send an ACK.

Comment 1 gnemas 2020-12-23 22:20:16 UTC
This issue is caused by https://fedoraproject.org/wiki/LTOByDefault

Fedora 33 enabled LTO by default, and this somehow breaks iperf.

Overriding the lto flags in the spec file fixes this issue.

This one-line change to the spec file fixes it:

diff --git a/iperf.spec b/iperf.spec
index 6512a09..ceeec11 100644
--- a/iperf.spec
+++ b/iperf.spec
@@ -18,6 +18,7 @@ jitter, datagram loss.
 %patch0 -p1

 %build
+%define _lto_cflags %{nil}
 autoconf
 %configure
 %{__make} %{?_smp_mflags}

Comment 2 Fedora Update System 2020-12-24 13:15:08 UTC
FEDORA-2020-11c341ca42 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-11c341ca42

Comment 3 Fedora Update System 2020-12-25 02:06:09 UTC
FEDORA-2020-11c341ca42 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-11c341ca42`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-11c341ca42

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2021-01-02 01:08:48 UTC
FEDORA-2020-11c341ca42 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.