Iperf 3.17.1 Windows build

[userdocs]

Just to clarify, you used the artifacts at the bottom of this link? https://github.com/userdocs/iperf3-static/actions/runs/11298286562 and not the current release asset?

[aflurko]

This explains everything, I was confused by the same compile date. Now I downloaded the artifacts from your link and it works correctly, my mistake

>iperf3.exe -s -p5201/2 -V
iperf 3.17.1+
CYGWIN_NT-10.0-19045 10 3.5.4-1.x86_64 2024-08-25 16:52 UTC x86_64
-----------------------------------------------------------
Server listening on 5201 (test #1)
-----------------------------------------------------------
Time: Sun, 13 Oct 2024 09:11:21 GMT
Accepted connection from x.y.net, port 60796
      Cookie: 53y6ht7sulcwdzpgag2ctvebh5du564rqa2n
      Target Bitrate: 1000000
[  5] local a.b.net port 5201 connected to x.y.net port 38808
[  6] local a.b.net port 5202 connected to x.y.net port 52453
Starting Test: protocol: UDP, 1 streams, 1460 byte blocks, omitting 0 seconds, 5 second test, tos 0
[ ID][Role] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5][RX-S]   0.00-1.00   sec   121 KBytes   992 Kbits/sec  0.027 ms  0/85 (0%)
[  6][TX-S]   0.00-1.00   sec   121 KBytes   992 Kbits/sec            85
[  5][RX-S]   1.00-2.00   sec   121 KBytes   989 Kbits/sec  0.053 ms  0/85 (0%)
[  6][TX-S]   1.00-2.00   sec   121 KBytes   989 Kbits/sec            86
[  5][RX-S]   2.00-3.00   sec   123 KBytes  1.00 Mbits/sec  0.033 ms  0/86 (0%)
[  6][TX-S]   2.00-3.00   sec   123 KBytes  1.00 Mbits/sec            86
[  5][RX-S]   3.00-4.00   sec   123 KBytes  1.01 Mbits/sec  0.042 ms  0/86 (0%)
[  6][TX-S]   3.00-4.00   sec   123 KBytes  1.01 Mbits/sec            85
[  5][RX-S]   4.00-5.00   sec   121 KBytes   991 Kbits/sec  0.041 ms  0/85 (0%)
[  6][TX-S]   4.00-5.00   sec   121 KBytes   991 Kbits/sec            86
[  5][RX-S]   5.00-5.02   sec  2.85 KBytes  1.32 Mbits/sec  0.054 ms  0/2 (0%)
[  6][TX-S]   5.00-5.02   sec  2.85 KBytes  1.32 Mbits/sec            1
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID][Role] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5] (sender statistics not available)
[  5][RX-S]   0.00-5.02   sec   612 KBytes   998 Kbits/sec  0.054 ms  0/429 (0%)  receiver
[  6][TX-S]   0.00-5.02   sec   612 KBytes   998 Kbits/sec  0.000 ms  0/429 (0%)  sender
[  6] (receiver statistics not available)
CPU Utilization: local/sender 0.6% (0.0%u/0.6%s), remote/receiver 0.0% (0.0%u/0.0%s)
CPU Utilization: local/receiver 0.6% (0.0%u/0.6%s), remote/sender 0.0% (0.0%u/0.0%s)
iperf 3.17.1+

 

[userdocs]

So the idea is to be able to run a workflow manually and pass if the repo and branch to get a builds as artifacts, not to interfere with the main releases. 

Because the repo builds both Linux and Windows builds, it can do it for both. Getting custom builds on demand. So the Linux and Windows builds were made using the custom repo and branch and uploaded as artifacts to those runs.

Even though it was mostly automated, I noticed some issues so I've updated the repo over the weekend to modernise it.

It now uses github attestations and virustotal in the build process to provide transparent build provenance from source, verified as it's built.

Linux has multiarch dockers available for releases via ghcr.io.

The way it's designed, anyone can fork the repo and use the workflows for themselves.

As it stands, it think this is probably the most complete and accessible method to get iperf3 static binaries.