• Sign in to Neowin Faster!

    Create an account on Neowin to contribute and support the site.

  • 0
Sign in to follow this  

Iperf 3.7 Windows build

Question

+BudMan    3,517

So there has been an on going thread about powerline adapters, well the OP finally got some - and I was curious about speed he is seeing, etc.  So told him would post up links to some tools.

 

This lead me to compiling the latest version of iperf3 I could find for windows ;) Since I couldn't find one.  So figured post it up if anyone is interested.

 

Got the source from here https://github.com/esnet/iperf

Found a blog post how to compile on windows here http://www.embeddedsystemtesting.com/2014/08/how-to-compile-iperf3-for-windows.html

 

So few minutes later I end up with a copy of the current iperf3 that works on windows.  Needs a few cygwin dlls, included in the zip.  But other than that unzip and go.

 

It has lots of new options compared to the older versions

 

Been a fan of iperf for years, so will prob keep this current when new versions come out since doesn't seem like anyone else is posting up the windows builds, etc.

You can grab all my compiled versions here https://files.budman.pw/

Any questions on its use, just ask -- post up some tests as well!!

 

edit: updated this on 02/25/17 new build 3.1.6

http://software.es.net/iperf/news.html#iperf-3-1-6-released

This version of iperf3 contains two minor fixes. Notably, one of them unbreaks JSON output with UDP tests.

 

edit2:  5/23/17 Thanks to @Datalink for letting me know site was down.  Back up now, if your having issues flush your dns had to move it to different host.  Added site to my monitoring so next time it goes down will know right away ;)

BTW 3.1.7 just typo's so no reason to compile it

2017-03-06: iperf-3.1.7 released

This version of iperf3 contains two documentation fixes, but is otherwise identical to the prior release.

 

edit3: 7/6/17 Updated to new 3.2 build

http://files.budman.pw/iperf3.2_32bit.zip

CRC32: 9e4b913c
MD5: ff7fc42f6ba29e9f83c8bb8e0066f722
SHA-1: 68ad3a0f0c2f30c1756f0a5eb39e1062e6beb6f4

http://files.budman.pw/iperf3.2_64bit.zip

CRC32: add96290
MD5: 7a014ff67b1d678f546ead2360820d47
SHA-1: 98ed98ac6d392a4484e5151ab2f714390c99b52e

 

edi4: 11/18/17 Updated to new 3.3 build

https://files.budman.pw/iperf3.3_64.zip

MD5: 49095ccb2442101d2a1ffc6213f3d1b9
SHA-256: 1fea7ae97b8ec5ab1c61ef1afcf7afd491d37ef41061a845f9bb8477425c66db

 

https://files.budman.pw/iperf3.3_32.zip

MD5: b6ad4c094a18196e0798e1a2825bc609
SHA-256: 919978ac0b574d7662d5b0e58174a6107002db96e7592929a9a28938516a2c5f

 

edit5: 02/16/2018 Updated to new 3.4 build see post in thread

https://files.budman.pw/iperf3.4_32.zip

MD5: 3b805d0895e7bb4d005429ed5859dd00
SHA-256: 82a933bbf96731a615ee5ae40bc1e6986ffcdd0b83c7c4e9cd024a996b3c0808
https://files.budman.pw/iperf3.4_64.zip

MD5: e4c0d2d8bda22ebbb710a9a65aacddf9
SHA-256: 7a3f83d211d22102d05dcf0eb24f4ff8cd3d9083aada9a27c88ba7ced0a0eccc

 

edit6: 03/05/2018 Updated to 3.5 build, see post in thread

https://files.budman.pw/iperf3.5_64.zip

CRC32: 18962237
MD5: 840a2d5e0f81d8a6dc0d8be854caf61a
SHA-1: 1a18185c79645b082392dcd024b7e53900dc38bd
SHA-256: 94a0ec4e486904a6a8ebe390eca37871f47a097599908c3647d6ad1d0bbdff59
 

https://files.budman.pw/iperf3.5_32.zip

CRC32: 21d8a0eb
MD5: dd79fe69c86e62c780e45e6e0d2ec66d
SHA-1: 2c63c1f9ef35be23170869a6a7eb048241aa2f14
SHA-256: bf4b95a58e54ceda101e33b0b908c581df1ce4a217f233e1092dc3278572de43

 

edit7:

https://files.budman.pw/iperf3.6_64bit.zip

CRC32: A9B23E64
MD5: 3530BD3C837EA146C8F98106FA94E395
SHA-1: 7E09239B207739714294A4EA1DA9C69623374740
SHA-256: DE958C4CF72DBC64DCBB42130BD466D9FD367E4519C5C3F78A6675CA87E12B7D

 

edit8: Updated 7/6/2019 New 3.7 build, see post in thread

https://files.budman.pw/iperf3.7_64.zip

CRC32: 13EB9AD9
MD5: 96C2C058B0128BEC346BD0D034D7B31E
SHA-1: 83978F54B7EDDA073CC4E865493AA6544862879A
SHA-256: 93FB4641810C06DE554E97FD4E6B44CEFBD8ECB8EA8CFEA3CC550B823C3E89CE

 

  • Like 12

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0
Dji    0

I reply to myself: error for missing diff is fixed (adding "diffutils" package) but still having error for missing nanosleep function)

Share this post


Link to post
Share on other sites
  • 0
Dji    0

Of found the "newbie" issue, I added "debug" packages instead of "Devel"...

Share this post


Link to post
Share on other sites
  • 0
Dji    0

Damn, this was not enough, I got a runtime error now:

> iperf3.exe
iperf3:./.libs/lt-iperf3.c:524: FATAL: error accessing file "/usr": No such file or directory.

 

Any idea ? :wacko:

Share this post


Link to post
Share on other sites
  • 0
+BudMan    3,517

I pretty much just installed cygwin and it compiled without errors..  I could do a clean cygwin install on a vm.. Sounds like to me your cygwin install is borked.  I see you see the blog post I used, since you posted your question there.  Did you make the edits to source that are listed in the blog post?

 

I did this, per the blog post

BudMan@i5-w7 /iperf-3.1b3
$ cd src
BudMan@i5-w7 /iperf-3.1b3/src
$ find ./ -iname "*.[ch]" |xargs -n1 sed -i s'#iprintf#newprintf#g'

 

End then edited src/iperf_api.c

char template[] = "/tmp/iperf3.XXXXXX";
to
char template[] = "./iperf3.XXXXXX";

 

edit:
Updated to build 3.1b3
updated Cygwin 2.1.0-1
$ uname -a
CYGWIN_NT-6.1 i5-w7 2.1.0(0.287/5/3) 2015-07-14 21:28 x86_64 Cygwin
 
BudMan@i5-w7 /usr/local/bin
$ cygcheck iperf3.exe
Found: C:\cygwin64\usr\local\bin\iperf3.exe
C:\cygwin64\usr\local\bin\iperf3.exe
  C:\cygwin64\bin\cygwin1.dll
    C:\Windows\system32\KERNEL32.dll
      C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
      C:\Windows\system32\ntdll.dll
      C:\Windows\system32\KERNELBASE.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll

BudMan@i5-w7 /usr/local/bin
 
D:\iperf3.1_b3>iperf3.exe -v
iperf 3.1b3
CYGWIN_NT-6.1 i5-w7 2.1.0(0.287/5/3) 2015-07-14 21:28 x86_64
Optional features available: None
 
D:\iperf3.1_b3>iperf3.exe -h
Usage: iperf [-s|-c host] [options]
       iperf [-h|--help] [-v|--version]

Server or Client:
  -p, --port      #         server port to listen on/connect to
  -f, --format    [kmgKMG]  format to report: Kbits, Mbits, KBytes, MBytes
  -i, --interval  #         seconds between periodic bandwidth reports
  -F, --file name           xmit/recv the specified file
  -B, --bind      <host>    bind to a specific interface
  -V, --verbose             more detailed output
  -J, --json                output in JSON format
  --logfile f               send output to a log file
  -d, --debug               emit debugging output
  -v, --version             show version information and quit
  -h, --help                show this message and quit
Server specific:
  -s, --server              run in server mode
  -D, --daemon              run the server as a daemon
  -I, --pidfile file        write PID file
  -1, --one-off             handle one client connection then exit
Client specific:
  -c, --client    <host>    run in client mode, connecting to <host>
  -u, --udp                 use UDP rather than TCP
  -b, --bandwidth #[KMG][/#] target bandwidth in bits/sec (0 for unlimited)
                            (default 1 Mbit/sec for UDP, unlimited for TCP)
                            (optional slash and packet count for burst mode)
  -t, --time      #         time in seconds to transmit for (default 10 secs)
  -n, --bytes     #[KMG]    number of bytes to transmit (instead of -t)
  -k, --blockcount #[KMG]   number of blocks (packets) to transmit (instead of -t or -n)
  -l, --len       #[KMG]    length of buffer to read or write
                            (default 128 KB for TCP, 8 KB for UDP)
  --cport         <port>    bind to a specific client port (TCP and UDP, default: ephemeral port)
  -P, --parallel  #         number of parallel client streams to run
  -R, --reverse             run in reverse mode (server sends, client receives)
  -w, --window    #[KMG]    set window size / socket buffer size
  -M, --set-mss   #         set TCP/SCTP maximum segment size (MTU - 40 bytes)
  -N, --no-delay            set TCP/SCTP no delay, disabling Nagle's Algorithm
  -4, --version4            only use IPv4
  -6, --version6            only use IPv6
  -S, --tos N               set the IP 'type of service'
  -Z, --zerocopy            use a 'zero copy' method of sending data
  -O, --omit N              omit the first n seconds
  -T, --title str           prefix every output line with this string
  --get-server-output       get results from server
  --udp-counters-64bit      use 64-bit counters in UDP test packets

[KMG] indicates options that support a K/M/G suffix for kilo-, mega-, or giga-

iperf3 homepage at: http://software.es.net/iperf/
Report bugs to:     https://github.com/esnet/iperf

D:\iperf3.1_b3>
 
Also -j option works

D:\iperf3.1_b3>iperf3.exe -s -J
{
        "start":        {
                "connected":    [{
                                "socket":       5,
                                "local_host":   "192.168.9.100",
                                "local_port":   5201,
                                "remote_host":  "192.168.9.8",
                                "remote_port":  49901
                        }],
                "version":      "iperf 3.1b3",
                "system_info":  "CYGWIN_NT-6.1 i5-w7 2.1.0(0.287/5/3) 2015-07-14 21:28 x86_64",
                "timestamp":    {
                        "time": "Tue, 21 Jul 2015 12:09:33 GMT",
                        "timesecs":     1437480573
                },
                "accepted_connection":  {
                        "host": "192.168.9.8",
                        "port": 49900
                },
                "cookie":       "storage.1437480588.553719.440b648674",
                "tcp_mss_default":      0,
                "test_start":   {
                        "protocol":     "TCP",
                        "num_streams":  1,
                        "blksize":      131072,
                        "omit": 0,
                        "duration":     10,
                        "bytes":        0,
                        "blocks":       0,
                        "reverse":      0
                }
        },
        "intervals":    [{
                        "streams":      [{
                                        "socket":       5,
                                        "start":        0,
                                        "end":  1,
                                        "seconds":      1,
                                        "bytes":        108701028,
                                        "bits_per_second":      869608224,
                                        "omitted":      false
 
<snipped>  Full output was too long to post

== iperf 3.1.0 ????-??-?? ==

The release notes for iperf 3.1.0 describe changes and new
functionality in iperf 3.1.0, but not present in 3.0.11 or any earlier
3.0.x release.

* Selected user-visible changes

  * SCTP support has been added (with the --sctp flag), on Linux,
    FreeBSD, and Solaris (issue #131).

  * Setting CPU affinity now works on FreeBSD.

  * Selection of TCP congestion now works on FreeBSD, and is now
    called --congestion (the old --linux-congestion option works
    but is now deprecated).

  * A new -I option for the server causes it to write a PID file,
    mostly useful for daemon mode (issue #120).

  * A --logfile argument can now force all output to go to a file,
    rather than to a file.  This is especially useful when running an
    iperf3 server in daemon mode (issue #119).

  * Various compatibility fixes for Android (issue #184, issue #185),
    NetBSD (issue #248), Solaris (issue #175, issue #178, issue #180,
    issue #211), vxWorks (issue #268).

  * A --udp-counters-64bit flag has been added to support very
    long-running UDP tests, which could cause a counter to overflow
    (issue #191).

  * A --cport option to specify the client-side port has been added
    (issue #207, issue #209, issue #239).

  * Some calculation errors with the -O feature have been fixed (issue
    #236).

  * A potential crash in the iperf3 server has been fixed (issue #257,
    issue #258).

  * Many miscellaneous bug fixes.

* Selected developer-visible changes

  * Consumers of libiperf can now get the JSON output for a
    just-completed test (issue #147).

  * Detection of various optional features has been improved to check
    for the presence or absence of platform functionality, not the name
    of platforms.

  * Out-of-tree builds now work (issue #265).

Updated first post in thread with new build number and link to file.

Share this post


Link to post
Share on other sites
  • 0
Dji    0

You're right, I found this morning, that I added "debug" package instead of "devel" .. (well well, I know)

 

Now it compiles (and works !) in x64 like a charm ! :)

Share this post


Link to post
Share on other sites
  • 0
Dji    0

BudMan, the x86 version you provided to us some month ago is not based on the same source code I've downloaded some days ago, even if it is the same version 3.0.11 (?!)

Some command line parameters are missing (particularly "--logfile"), so I've recompiled it.

For the ones who are interested in, here is iperf 3.0.11 for x64 and x86 including the corresponding html documentation : http://www.audouy.fr/share/iperf3.7z

Hope it will help :)

Regards,

Dji.

Share this post


Link to post
Share on other sites
  • 0
+BudMan    3,517

Yeah I switched over to 64 bit a few versions back, I can do a 32 bit version sure.. If work doesn't get to hectic today will do pretty soon - if not later tonight or tmrw morning when I get home.. I will do the 3.0.11 version and the new 3.1b3 version in 32bit for those still 32 bit ;)

 

Where did you get source from - I was not aware of any different revision in code for the 3.0.11

Share this post


Link to post
Share on other sites
  • 0
Dji    0

Of course, I've downloaded sources from github repository: https://github.com/esnet/iperf

 

Well for my really specific needs, I need both x86 and x64 for server side (because I have to install it from Windows 20012 x64 to Windows 2003 x86 servers... yes still exists !) but only x64 for client side (Windows PE 4.0 x64)

Share this post


Link to post
Share on other sites
  • 0
+BudMan    3,517

Yeah I can understand that there are some 32bit stuff out there.. I got side tracked yesterday and didn't get a chance to upload the 32bit version.  But sounds like you compiled yourself.. But there may be others in your situation so I will start putting both 32 and 64 bit versions out there.

 

I am no guru in compiling stuff, but basic stuff like this is fairly straight forward and easy to test working, etc.  And I have plenty of server space and bandwidth so if I can help out the next guy looking for a windows version of this great software I love doing it.

 

I wish I could figure out how I could compile it to run on windows without cygwin dll, etc. I did a bit of research if possible to imbed the dll in the ext but from my quick search doesn't seem like something that is supported by cygwin.

Share this post


Link to post
Share on other sites
  • 0
cybrnook    0

Thank you for this @ +BudMan

Share this post


Link to post
Share on other sites
  • 0
+BudMan    3,517

well I built the 32 bit versions the other day, but on neowin was down.  And now I am on the road - prob have to wait til I get back home to post them up.

Share this post


Link to post
Share on other sites
  • 0
Aergan    622

well I built the 32 bit versions the other day, but on neowin was down.  And now I am on the road - prob have to wait til I get back home to post them up.

Working fine here, many thanks. I'd had issues with performance consistency with a previous build.

Are cyggcc_s-1.dll and cygstdc++-6.dll still required?

Share this post


Link to post
Share on other sites
  • 0
+BudMan    3,517

So look at the cygcheck output it lists the dlls that are used.  I will be posting up the other builds here as soon as I get some coffee ;)

 

edit: ok updated the front page with links to the 32bit versions.  The 32bit one of 3.11 still shows it needed this cygwin1 and cyggcc_s-1.dll

$ cygcheck iperf3.exe
Found: D:\cygwin\usr\local\bin\iperf3.exe
D:\cygwin\usr\local\bin\iperf3.exe
  D:\cygwin\bin\cygwin1.dll
    C:\Windows\system32\KERNEL32.dll
      C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
      C:\Windows\system32\ntdll.dll
      C:\Windows\system32\KERNELBASE.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll
  D:\cygwin\bin\cyggcc_s-1.dll

BudMan@i5-w7 /usr/local/bin

Edited by BudMan
  • Like 1

Share this post


Link to post
Share on other sites
  • 0
+BudMan    3,517

So 3.1 released today... So have compiled both 32 and 64 bit, also updated cygwin to 2.2.1

Here are the details. https://github.com/esnet/iperf

= iperf 3.1 2015-10-16 ==

The release notes for iperf 3.1 describe changes and new
functionality in iperf 3.1, but not present in 3.0.11 or any earlier
3.0.x release.

* Selected user-visible changes

  * SCTP support has been added (with the --sctp flag), on Linux,
    FreeBSD, and Solaris (issue #131).

  * Setting CPU affinity now works on FreeBSD.

  * Selection of TCP congestion now works on FreeBSD, and is now
    called --congestion (the old --linux-congestion option works
    but is now deprecated).

  * A new -I option for the server causes it to write a PID file,
    mostly useful for daemon mode (issue #120).

  * A --logfile argument can now force all output to go to a file,
    rather than to a file.  This is especially useful when running an
    iperf3 server in daemon mode (issue #119).

  * Various compatibility fixes for Android (issue #184, issue #185),
    iOS (issue #288), NetBSD (issue #248), Solaris (issue #175, issue
    #178, issue #180, issue #211), vxWorks (issue #268).

  * A --udp-counters-64bit flag has been added to support very
    long-running UDP tests, which could cause a counter to overflow
    (issue #191).

  * A --cport option to specify the client-side port has been added
    (issue #207, issue #209, issue #239).

  * Some calculation errors with the -O feature have been fixed (issue
    #236).

  * A potential crash in the iperf3 server has been fixed (issue #257,
    issue #258).

  * Many miscellaneous bug fixes.

* Selected developer-visible changes

  * Consumers of libiperf can now get the JSON output for a
    just-completed test (issue #147).

  * Detection of various optional features has been improved to check
    for the presence or absence of platform functionality, not the name
    of platforms.

  * Out-of-tree builds now work (issue #265).

$ cygcheck.exe iperf3.exe
Found: C:\cygwin64\usr\local\bin\iperf3.exe
C:\cygwin64\usr\local\bin\iperf3.exe
  C:\cygwin64\bin\cygwin1.dll
    C:\Windows\system32\KERNEL32.dll
      C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
      C:\Windows\system32\ntdll.dll
      C:\Windows\system32\KERNELBASE.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll

BudMan@i5-w7 /usr/local/bin

D:\iperf3.1_64>iperf3.exe -v
iperf 3.1
CYGWIN_NT-6.1 i5-w7 2.2.1(0.289/5/3) 2015-08-20 11:42 x86_64
Optional features available: None

32bit version

BudMan@i5-w7 /usr/local/bin
$ iperf3.exe -v
iperf 3.1
CYGWIN_NT-6.1-WOW i5-w7 2.2.1(0.289/5/3) 2015-08-20 11:40 i686
Optional features available: None

BudMan@i5-w7 /usr/local/bin
$ cygcheck.exe iperf3.exe
Found: D:\cygwin\usr\local\bin\iperf3.exe
D:\cygwin\usr\local\bin\iperf3.exe
  D:\cygwin\bin\cygwin1.dll
    C:\Windows\system32\KERNEL32.dll
      C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
      C:\Windows\system32\ntdll.dll
      C:\Windows\system32\KERNELBASE.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll
  D:\cygwin\bin\cyggcc_s-1.dll

BudMan@i5-w7 /usr/local/bin

D:\iperf3.1_32>iperf3.exe -v
iperf 3.1
CYGWIN_NT-6.1-WOW i5-w7 2.2.1(0.289/5/3) 2015-08-20 11:40 i686
Optional features available: None

D:\iperf3.1_32>

 

 

 

 

Share this post


Link to post
Share on other sites
  • 0
+BudMan    3,517

ok updated to 3.1.1, updated cygwin to 2.3.1

 

BudMan@i5-w7 /usr/local/bin
$ ./iperf3.exe -v
iperf 3.1.1
CYGWIN_NT-6.1 i5-w7 2.3.1(0.291/5/3) 2015-11-14 12:44 x86_64
Optional features available: None

BudMan@i5-w7 /usr/local/bin
$ cygcheck.exe iperf3.exe
Found: C:\cygwin64\usr\local\bin\iperf3.exe
C:\cygwin64\usr\local\bin\iperf3.exe
  C:\cygwin64\bin\cygwin1.dll
    C:\Windows\system32\KERNEL32.dll
      C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
      C:\Windows\system32\ntdll.dll
      C:\Windows\system32\KERNELBASE.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll

BudMan@i5-w7 /usr/local/bin
$

 

The 32bit version shows that it needs cyggcc_s-1.dll as well, so that is included in the 32bit zip.

 

== iperf 3.1.1 2015-11-19 ==

The release notes for iperf 3.1.1 describe changes and new
functionality in iperf 3.1.1, but not present in 3.1.

* User-visible changes

  * Some markup fixes have been made in the manpages for Debian
    compatibility (issue #291).

  * A bug where the -T title option was not being output correctly
    in JSON output has been fixed (issue #292).

  * Argument handling for some command-line options has been improved
    (issue #316).

* Developer-visible changes

  * A regression with C++ compatibility in one of the iperf header
    files has been fixed (issue #323).

 

files can be found here

http://files.budman.pw/iperf3.1.1_64.zip

http://files.budman.pw/iperf3.1.1_32.zip

 

Share this post


Link to post
Share on other sites
  • 0
+BudMan    3,517

Updated to 3.1.2 both 32 and 64, updated first post in thread with new download links

 

Or you can just go here and browse http://files.budman.pw

 

This release fixes a couple of minor bugs, including one that results in invalid JSON being emitted for UDP tests.

Share this post


Link to post
Share on other sites
  • 0
+BudMan    3,517

Updated to 3.1.3 both 32 and 64, and 3.0.12 both 32 and 64.  Updated first post in thread with new download links

 

Or you can just go here and browse http://files.budman.pw

 

sha256 for the new files are

98798CE0062217E0FF3F095AD56DA1A0DE5607FE    iperf3.1.3_32.zip
84B707F94005A70AA5B5373A47D9B00C55ED6C63    iperf3.0.12_32.zip
7AB40186AEC5490C8A6F34776D4FE09B073A62BC    iperf3.1.3_64.zip
4B10AC4227267AC0724F75B360A82D1808F93534    iperf3.0.12_64.zip

 

md5 of the new files are

6C30678073E6A180B197E1CFB8E27262    iperf3.0.12_32.zip
3439BF23397D16C5F44434DF3278669C    iperf3.1.3_32.zip
495B469D8FFF51E872F57CD47A07F09B    iperf3.0.12_64.zip
3218D0D8E067FB55F2CA9B3F647AE90B    iperf3.1.3_64.zip

 

Share this post


Link to post
Share on other sites
  • 0
+BudMan    3,517

Updated both 32 and 64 bit to 3.1.4 using latest cygwin 2.6.0, updated first post in thread with new download links

 

Or you can just go here and browse http://files.budman.pw


Budman@I5-WIN C:\build\iperf_3.1.4_32
> iperf3.exe -v
iperf 3.1.4
CYGWIN_NT-6.3-WOW i5-win 2.6.0(0.304/5/3) 2016-08-31 14:27 i686
Optional features available: None

 

Budman@I5-WIN C:\build\iperf_3.1.4_64
> iperf3.exe -v
iperf 3.1.4
CYGWIN_NT-6.3 i5-win 2.6.0(0.304/5/3) 2016-08-31 14:32 x86_64
Optional features available: None

 

File: iperf_3.1.4_32.zip
CRC-32: 7ff84eef
MD5: a8c7536370d5886269418dfe1cb5adf4
SHA-1: 10e06f0f5e81de881f3da806b6c1e0ad4c9f4e07

 

File: iperf_3.1.4_64.zip
CRC-32: 01507ea5
MD5: 878277454ff14cadc52af0839f55fd46
SHA-1: a0aad4d2429634d3408a90ab6d24a2792aedecbb

  • Like 1

Share this post


Link to post
Share on other sites
  • 0
+BudMan    3,517

updated  to 3.1.5 using latest cygwin 2.6.1

 

http://files.budman.pw

 

Budman@I5-WIN C:\iperf\iperf3.1.5_32
> iperf3.exe -v
iperf 3.1.5
CYGWIN_NT-6.3-WOW i5-win 2.6.1(0.305/5/3) 2016-12-16 11:50 i686
Optional features available: None

 

Budman@I5-WIN C:\iperf\iperf3.1.5_64
> iperf3.exe -v
iperf 3.1.5
CYGWIN_NT-6.3 i5-win 2.6.1(0.305/5/3) 2016-12-16 11:55 x86_64
Optional features available: None

 

iperf3.1.5_32.zip

CRC32: 893af4ec
MD5: 445689c8344ced172930c508174e1bb8
SHA-256: ef12541b8ed10510cc8f0c08bae353be1065a2a49ab0f68c1a162a4a681f5ac3

 

iperf3.1.5_64.zip

CRC32: f2d11a99
MD5: 28828388a16fb458ab41994cce68640b
SHA-256: efe14c556a285e9651ddd4c3be33b583a4e0c962959d6199e0f9d5b5757022a9

Share this post


Link to post
Share on other sites
  • 0
+BudMan    3,517

Updated to 3.1.6 using latest cygwin 2.7

 

http://files.budman.pw

 

Budman@I5-WIN D:\iperf3.1.6_64bit
> iperf3.exe -v
iperf 3.1.6
CYGWIN_NT-6.3 i5-win 2.7.0(0.306/5/3) 2017-02-12 13:18 x86_64
Optional features available: None

 

File: iperf3.1.6_32bit.zip
CRC-32: 9a4953c2
MD5: 560d83225a6b9b6a0ec3cd6dedbb3b63
SHA-1: 627e11542df56ab1f64a0c89372eb7718717b3a5

 

File: iperf3.1.6_64bit.zip
CRC-32: 32a446a3
MD5: db88fd4e4f65dc5082d021874970c44f
SHA-1: cd0273f20dbe2bcaf704815db87ef34ccb55959b

 

Share this post


Link to post
Share on other sites
  • 0
+BudMan    3,517

New 3.2 build out

 

Budman@I5-WIN D:\iperf3.2_32bit
> iperf3.exe -v
iperf 3.2 (cJSON 1.5.2)
CYGWIN_NT-6.3-WOW i5-win 2.8.1(0.312/5/3) 2017-07-03 14:06 i686
Optional features available: authentication

 

Budman@I5-WIN D:\iperf3.2_64bit
> iperf3.exe -v
iperf 3.2 (cJSON 1.5.2)
CYGWIN_NT-6.3 i5-win 2.8.1(0.312/5/3) 2017-07-03 14:11 x86_64
Optional features available: authentication

 

http://files.budman.pw/iperf3.2_32bit.zip

CRC32: 9e4b913c
MD5: ff7fc42f6ba29e9f83c8bb8e0066f722
SHA-1: 68ad3a0f0c2f30c1756f0a5eb39e1062e6beb6f4

http://files.budman.pw/iperf3.2_64bit.zip

CRC32: add96290
MD5: 7a014ff67b1d678f546ead2360820d47
SHA-1: 98ed98ac6d392a4484e5151ab2f714390c99b52e
 

Share this post


Link to post
Share on other sites
  • 0
Marshall    15,357

Eset doesn't like your share, @BudMan

 

 

snag.jpg

 

:)

  • Like 1

Share this post


Link to post
Share on other sites
  • 0
+BudMan    3,517

Really?  Thanks I will look into - but the only thing on there are iperf zips and md5 files.. But thanks for bring that to my attention.  Do you have a link that explains why?  I will try and query the eset database.

 

Wow that company freaking sucks!  I have to email them and wait 2 days maybe?  And they don't list WHY its listed..

 

it shows clean on every scanner I check..  Other then them..

 

scan.thumb.png.943469e6a0955c10e9b2f4bf93003521.png

 

Total virus shows it clean - other than eset.. Such BS!!  Thanks for bringing to my attention!  If you could report it in your tool as false and let them rescan it that would be great, I already have email out to samples@eset.com to have them double check.. Some actual details of what they detected.. Your not going to list what is detected, then your full of it!!

  • Like 1

Share this post


Link to post
Share on other sites
  • 0
Marshall    15,357

Unflagged as false positive.

 

Apparently they fixed the isssue, I'm able to get to that URL without disabling Eset now.

  • Like 1

Share this post


Link to post
Share on other sites
  • 0
+BudMan    3,517

Yeah just got this email few hours ago

unblocked.thumb.png.2f4122fb09f8ad18f0c1259da9d73b9a.png

 

Thanks for bringing to my attention @Marshall

 

And now virustotal scan shows clean on all 66, the eset listing is gone

scan.thumb.png.45eed021dbb8f6f788969787810af2df.png

 

  • Like 2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.