The server stopped statistics on the 7th hour in the continuous testing

[zhangshuai75]

Two AMR64 boards were used for testing. Iperf version is 3.13. The commands on the server and client are as follows:
Server: iperf3 -s -p 1234 -4
Client : iperf3 -c 10.169.86.100 -p 1234 -4 -u -b 1000M -t 46800
It is scheduled to run for 13 hours, but an error occurs in server-side statistics at the 7th hour. The log looks like this:

root@root:~# iperf3 -s -p 1234 -4 -V
iperf 3.11
Linux 6.1.33-00002-g1653592bb2c7-dirty #1 SMP PREEMPT Fri Oct 20 06:18:30 UTC 2023 aarch64
-----------------------------------------------------------
Server listening on 1234 (test #1)
-----------------------------------------------------------
Time: Mon, 11 Dec 2023 17:50:43 GMT
Accepted connection from 10.169.86.101, port 33702
      Cookie: tt5ayat2thzac3ldwnkukx6xjankckfejrcb
      Target Bitrate: 1000000000
[  5] local 10.169.86.100 port 1234 connected to 10.169.86.101 port 52574
Starting Test: protocol: UDP, 1 streams, 1448 byte blocks, omitting 0 seconds, 46800 second test, tos 0
[ ID] Interval                  Transfer           Bitrate           Jitter      Lost/Total Datagrams
[  5]   0.00-1.00   sec   106 MBytes   892 Mbits/sec  0.005 ms  0/76973 (0%)
[  5]   1.00-2.00   sec   106 MBytes   893 Mbits/sec  0.004 ms  0/77062 (0%)
[  5]   2.00-3.00   sec   108 MBytes   903 Mbits/sec  0.004 ms  0/77995 (0%)
[  5]   3.00-4.00   sec   114 MBytes   955 Mbits/sec  0.005 ms  0/82480 (0%)
……
[  5] 26272.00-26273.00 sec   114 MBytes   956 Mbits/sec  0.004 ms  0/82546 (0%)
[  5] 26273.00-26274.00 sec   114 MBytes   956 Mbits/sec  0.004 ms  0/82547 (0%)
[  5] 26274.00-26275.00 sec   114 MBytes   956 Mbits/sec  0.005 ms  0/82554 (0%)
[  5] 26275.00-26276.00 sec   114 MBytes   956 Mbits/sec  0.004 ms  0/26045 (0%)
[  5] 26276.00-26277.00 sec   114 MBytes   956 Mbits/sec  0.004 ms  0/0 (0%)
[  5] 26277.00-26278.00 sec   114 MBytes   956 Mbits/sec  0.005 ms  0/0 (0%)
[  5] 26278.00-26279.00 sec   114 MBytes   956 Mbits/sec  0.005 ms  0/0 (0%)
[  5] 26279.00-26280.00 sec   114 MBytes   956 Mbits/sec  0.004 ms  0/0 (0%)
[  5] 26280.00-26281.00 sec   114 MBytes   956 Mbits/sec  0.005 ms  0/0 (0%)
……

[  5] 46793.00-46794.00 sec   114 MBytes   956 Mbits/sec  0.006 ms  0/0 (0%)
[  5] 46794.00-46795.00 sec   114 MBytes   956 Mbits/sec  0.007 ms  0/0 (0%)
[  5] 46795.00-46796.00 sec   114 MBytes   956 Mbits/sec  0.005 ms  0/0 (0%)
[  5] 46796.00-46797.00 sec   114 MBytes   956 Mbits/sec  0.004 ms  0/0 (0%)
[  5] 46797.00-46798.00 sec   114 MBytes   956 Mbits/sec  0.005 ms  0/0 (0%)
[  5] 46798.00-46798.78 sec  88.5 MBytes   956 Mbits/sec  0.004 ms  0/0 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5] (sender statistics not available)
[SUM]  0.0-46798.8 sec  1679008482 datagrams received out-of-order
[  5]   0.00-46798.78 sec  5.04 TBytes   947 Mbits/sec  0.004 ms  0/2147483647 (0%)  receiver
iperf 3.11

I repeated the experiment and the results were still similar.

[davidBar-On]

This is an overflow issue that was fixed in iperf3.14 by PR #1536. Note that the reported 2147483647 total number of packets is 0x7fffffff, and is the same as reported in issue #1534 that was fixed by #1536.