Crashing with SIGSYS on r = sendfile(fromfd, tofd, offset, &sent, NULL, 0);, do older versions of iOS support sendfile? There may be a way to detect that.

Attemping to set the protocol to UDP via the method -

set_protocol(test , 2);

Sets all the test protocol items correctly for UDP (analysed through breakpoints). But socket writing always fails, and sometimes mentions No such File or directory exists?

When using an ipv4 address as opposed to hostname I receive the message „unable to connect to server“. The resolvable hostname works fine the server has both an ipv4 and IPv6 address - the IPv6 address works too

When i trying this code in xcode a code error IPFHelpViewController.h file is not found. how to resolve this error? and how to use c file in objective c?

This is what the logs look like:

Warning: Attempt to present <UIAlertController: 0x7fb9aa818e00>  on <IPFTestRunnerViewController: 0x7fb9a9f10fa0> which is already presenting (null)`

Right now we only have the iperf license in the repo, look at it to see if it is compatible with App Store release and can cover the ObjC code as well, or pick another license.

I am using an Ipad pro running 14.4.1, connecting to a server running on a mac.

Transmit mode upload, streams 1, test duration 10s.

I click start and I get "unknown error 114 running the test". I try again and get the same error. I try again and this time no error.. I just get "..." displayed below.

I wait 10 seconds and nothing happens. I click "Stop", nothing happens.

The server logs indicate it's connecting, but almost nothing is sent:

------------------------------------------------------------
Server listening on TCP port 5001
TCP window size:  128 KByte (default)
------------------------------------------------------------
[  4] local 192.168.1.6 port 5001 connected with 192.168.1.123 port 52998 (peer 112.28467.27250-unk)
[  5] local 192.168.1.6 port 5001 connected with 192.168.1.123 port 52999 (peer 98.30308.30839-unk)
[  6] local 192.168.1.6 port 5001 connected with 192.168.1.123 port 53000
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-62.4 sec  37.0 Bytes  4.75 bits/sec
[  5]  0.0-62.4 sec  37.0 Bytes  4.75 bits/sec
[  6]  0.0-62.4 sec  37.0 Bytes  4.75 bits/sec
[SUM]  0.0-62.4 sec   111 Bytes  14.2 bits/sec

I also tried download, and I got error 114 6 times, and then the "..."

Hi,

I am integrating iperf in framework I am developing in objective c for iOS and macOS. After copying source files of iperf3.0 (c files), I am getting error on iOS/macOS system files like NSObject, AppKit.h etc. I am not sure what I am missing. But iperf files showing error for arm64 like in screenshot attached.

Universal Framework Minimum Target: iOS: 11.0 macOS: 10.11

Shared code for iOS and macOS framework developed mainly in Objective C

I saw a link from the iOS App Store to this Github page, but didn't see a link from this page to the iOS App Store. Not sure if there is any license issue from preventing this...

Latest proposal:

• take Apple's Wifi icon
• render it using the olympic colors, one per stripe
• alternatively render the full circle
• in the app, fill the rings as the tests progress

Look at the Tokyo 2020 logos for inspiration (see the color scheme too).

Right now you pick a test duration, hit start and wait until the results come back. I don't know if the protocol supports it, but starting the test and stopping it when you are happy with the results is a better user experience.

As I mostly use the app to compare the speeds of the mobile operators I use, it would be really time-saving to have a option to switch between a test based von IPv4 and IPv6 as a transport protocol. Of course this only makes sense as long as a Hostname with IPv4 and IPv6 address is used for the test. The CLI-based clients have a similar option while using the -4 and -6 flags and drop a error if the given server does not support IPv4 or IPv6 depending on the given flag.

It would be great to be able to use the Shortcuts app to control iperf. It would then be possible to run tests automatically. For example, you could run a test daily or you could run a test when you connect to a new network or based on some other trigger like that.

A good iPerf testing article that goes into the different advanced options. Window size and UDP might be interesting to surface in the UI.

Jitter recommendations:

Ideally, jitter should be below 30ms. Packet loss should be no more than 1%, and network latency shouldn’t exceed 150 ms one-way (300 ms return).

Test run with 20 Mbits/s (but unidirectional and single stream) to match a FaceTime connection:

% iperf3 -uc 192.168.6.11 -b 20M
Connecting to host 192.168.6.11, port 5201 [ 5] local 192.168.6.60 port 53073 connected to 192.168.6.11 port 5201 [ ID] Interval Transfer Bitrate Total Datagrams [ 5] 0.00-1.00 sec 2.38 MBytes 20.0 Mbits/sec 1726
[ 5] 1.00-2.00 sec 2.38 MBytes 20.0 Mbits/sec 1726
[ 5] 2.00-3.00 sec 2.38 MBytes 20.0 Mbits/sec 1727
[ 5] 3.00-4.00 sec 2.38 MBytes 20.0 Mbits/sec 1726
[ 5] 4.00-5.00 sec 2.38 MBytes 20.0 Mbits/sec 1727
[ 5] 5.00-6.00 sec 2.38 MBytes 20.0 Mbits/sec 1726
[ 5] 6.00-7.00 sec 2.38 MBytes 20.0 Mbits/sec 1727
[ 5] 7.00-8.00 sec 2.38 MBytes 20.0 Mbits/sec 1726
[ 5] 8.00-9.00 sec 2.38 MBytes 20.0 Mbits/sec 1727
[ 5] 9.00-10.00 sec 2.38 MBytes 20.0 Mbits/sec 1726

---

[ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams [ 5] 0.00-10.00 sec 23.8 MBytes 20.0 Mbits/sec 0.000 ms 0/17264 (0%) sender [ 5] 0.00-10.00 sec 23.8 MBytes 20.0 Mbits/sec 0.210 ms 0/17264 (0%) receiver

iperf Done.

Bugs like #46 and #47 lack diagnostic data that would help understand why tests fail or the app fails to connect to the server, let's see if we can surface herror / perror to give people full context