Closed GoogleCodeExporter closed 9 years ago
$ make check
Making check in src
make check-TESTS
./t_timer[2]: syntax error: `(' unexpected
FAIL: t_timer
./t_units[1]: syntax error: `(' unexpected
FAIL: t_units
./t_uuid[1]: syntax error: `(' unexpected
FAIL: t_uuid
==================================================
3 of 3 tests failed
Please report to iperf-users@lists.sourceforge.net
==================================================
*** Error 1 in src (Makefile:1005 'check-TESTS': @failed=0; all=0; xfail=0;
xpass=0; skip=0; srcdir=.; export srcdir; list='t_timer t_uni...)
*** Error 1 in src (Makefile:1035 'check-am')
*** Error 1 in /home/mleonard/iperf (Makefile:257 'check-recursive')
$ uname -a
OpenBSD it-na-rrf-pro-01-00p 5.4 GENERIC.MP#41 amd64
$
Original comment by thepurpl...@gmail.com
on 13 Nov 2013 at 9:53
We should find an OpenBSD machine to try this on.
Original comment by jef.posk...@gmail.com
on 16 Dec 2013 at 6:51
We think this is fixed now. Can you test with the latest tar file?
Original comment by bltier...@es.net
on 18 Dec 2013 at 9:37
Original comment by bltier...@es.net
on 18 Dec 2013 at 10:42
It compiles and runs, but I'm now seeing a different error:
(I ran it once as a regular user with the same result as below)
$ sudo iperf3 -c bernoullinetworks.com
Connecting to host <mytesthost>, port 5201
[ 4] local <localmachineIP> port 46768 connected to <mytesthost> port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.04 sec 2.75 MBytes 22.2 Mbits/sec
[ 4] 1.04-2.02 sec 3.62 MBytes 31.1 Mbits/sec
[ 4] 2.02-3.05 sec 2.00 MBytes 16.3 Mbits/sec
[ 4] 3.05-4.03 sec 3.38 MBytes 28.8 Mbits/sec
[ 4] 4.03-5.01 sec 3.62 MBytes 31.1 Mbits/sec
[ 4] 5.01-6.05 sec 2.25 MBytes 18.1 Mbits/sec
[ 4] 6.05-7.04 sec 2.38 MBytes 20.2 Mbits/sec
[ 4] 7.04-8.01 sec 2.25 MBytes 19.3 Mbits/sec
[ 4] 8.01-9.06 sec 1.38 MBytes 11.0 Mbits/sec
iperf3: error - unable to receive results: Cannot allocate memory
$
Original comment by thepurpl...@gmail.com
on 19 Dec 2013 at 2:31
I did a quick test on an OpenBSD 5.4 / amd64 system, using iperf3 from the tip
of the default branch.
I was able to make this work, both doing tests to localhost and to a FreeBSD
server, without any particular incident. The main issue I saw is that (as
currently configured) I needed to specify -4 on the OpenBSD iperf3 server, or
else I got an "Invalid argument" when trying to create the listening socket.
It's entirely possible that there's something in my OpenBSD VM that isn't
configured correctly, particularly since I'm a completely newbie on OpenBSD
(I'm more of a FreeBSD person). This seemed to have a decent workaround
however.
Original comment by bmah@es.net
on 6 Jan 2014 at 7:30
@thepurplebuffalo: With the iperf3 3.0.1 release out the door, would you be
able to test with that code and see if you still see the problem? In Comment 6
I had it mostly working with pre-release code (and re-tested just now with
post-3.0.1 code).
Original comment by bmah@es.net
on 21 Jan 2014 at 9:18
Compiles, make check looks happy, will not run:
$ pwd
/home/mleonard/iperf-3.0.1
$ make check
Making check in src
make check-TESTS
PASS: t_timer
PASS: t_units
cookie: 'it-na-rrf-pro-01-00p.13903'
PASS: t_uuid
==================
All 3 tests passed
==================
$ iperf3 -v
iperf version 3.0.1 (10 January 2014)
OpenBSD it-na-rrf-pro-01-00p 5.4 GENERIC.MP#41 amd64
$ iperf3 -s
iperf3: error - unable to start listener for connections: Invalid argument
iperf3: error - unable to start listener for connections: Invalid argument
iperf3: error - unable to start listener for connections: Invalid argument
iperf3: error - unable to start listener for connections: Invalid argument
iperf3: error - unable to start listener for connections: Invalid argument
too many errors, exiting
$
Original comment by thepurpl...@gmail.com
on 21 Jan 2014 at 9:31
Disregard my last.
I added the "-4" and it worked fine as a daemon. It's also working fine as a
client.
THANKS!
Original comment by thepurpl...@gmail.com
on 21 Jan 2014 at 9:36
OK, thanks for the report. I added a note to the README about needing -4 on
OpenBSD. Closing this as fixed for now, since iperf3 is working with this
small workaround.
Original comment by bmah@es.net
on 22 Jan 2014 at 12:14
Original issue reported on code.google.com by
thepurpl...@gmail.com
on 13 Nov 2013 at 9:45