Hi Daniel, Bob, et al--

ESnet only distributes source code for iperf3...we don't provide
binaries for Windows or any other platform.  (I'm aware people have
gotten it to compile with Cygwin, and we've done some portability fixes
to help with that, even though it's not an explicitly supported
platform.)  But it really sounds like this is an issue with third
parties who are building it and making those executables available.
There isn't anything we can do at a source code level.

Bruce.

If memory serves me right, Bob McMahon via Iperf-users wrote:
> Bruce Mah at es net is my main iperf 3 contact.
> 
> Not sure what you mean by "I hope they don't set a fixed size buffer"
> 
> FYI, the current git head of iperf 2.0.14 hasn't undergone any windows
> testing yet.  Not sure if it even compiles.  The 2.0.13 tarball is the
> latest official release. 
> 
> We're getting closer to a 2.0.14 release - feel free to
> request features. https://youtu.be/pfzwrcTDc38
> 
> Bob
> 
> On Tue, Feb 4, 2020 at 2:28 PM Daniel Havey <dha...@gmail.com
> <mailto:dha...@gmail.com>> wrote:
> 
>     Okay cool.  I hope they didn't set a fixed buffer size.  I will
>     download iperf2 and try it out.  I'll let you know how if there
>     are any issues.  BTW: Do you know who is responsible for iperf3? 
>     That's the tool that I have been getting limited bandwidth reports on.
> 
>     On Tue, Feb 4, 2020 at 2:23 PM Bob McMahon <bob.mcma...@broadcom.com
>     <mailto:bob.mcma...@broadcom.com>> wrote:
> 
>         I just checked with our windows engineer and he said the iperf 2
>         <https://sourceforge.net/projects/iperf2/>team no longer uses
>         cygwin but rather builds a native version.
> 
>         Bob
> 
>         On Tue, Feb 4, 2020 at 2:07 PM Daniel Havey <dha...@gmail.com
>         <mailto:dha...@gmail.com>> wrote:
> 
>             Hi, I'm Daniel Havey from Microsoft Windows.  I'm the PM for
>             transports (TCP/QUIC) and there is a bug in the cygwin1.dll
>             that was distributed with the iperf binaries.  The bug
>             limits maximum bandwidth achievable by the iperf tool. 
>             Details can be found in my
>             blogpost: 
> https://techcommunity.microsoft.com/t5/networking-blog/windows-network-performance-suffering-from-bad-buffering/ba-p/339668
> 
>             We worked with RedHat on Cygwin to fix the bug, but I am
>             still getting reports of limited bandwidth from windows
>             iperf users.  The fix is simple.  Just download the new
>             cygwin1.dll from the cygwin website and the problem will
>             be fixed.
> 
>             thanks ;)
>             ...Daniel
>             _______________________________________________
>             Iperf-users mailing list
>             Iperf-users@lists.sourceforge.net
>             <mailto:Iperf-users@lists.sourceforge.net>
>             https://lists.sourceforge.net/lists/listinfo/iperf-users
> 
> 
> 
> _______________________________________________
> Iperf-users mailing list
> Iperf-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/iperf-users
> 


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Iperf-users mailing list
Iperf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iperf-users

Reply via email to