I had 2.0.4 packaged and ready to submit the day I read on NANOG that 2.0.4 was
released, a few months ago :)

Then I noticed that in server mode ('iperf -s') the server quits, with a 0
exit code nonetheless, any time I try to connect to it in bidirectional mode.

Try running 2.0.4 in simple server mode on machine foo:

    [somlo@foo]$ iperf -s

then connect to it in duplex mode from machine bar:

    [somlo@bar]$ iperf -c foo -d

When I tried it, on foo, the iperf server terminated at the end of the test.

I submitted a message to their mailing list about this, never got any replies.

I could fix it if it were C, but tracking down where things happen across a
bunch of objects in C++ is more time consuming than my schedule permits.

If I had to make a judgment call, I'd say having a broken daemon mode is less
bad than having a broken duplex mode, but I realize that's not a good answer.

Let me try to ping them again on the duplex issue, but meanwhile if you know
C++ and want to track down where it decides to exit instead of continuing to
listen after a duplex client connection, I'd appreciate a cc when you send in
the patch :)

Thanks,
Gabriel

so, apparently, sending stuff to the mailing list is equivalent to sending to
/dev/null :)

Hidden on the sourceforge page somewhere, there was a link to a bug tracker. I
just submitted the following:

https://sourceforge.net/tracker/index.php?func=detail&aid=1983829&group_id=128336&atid=711371

Let's see if that helps speed things up...

iperf-2.0.4-1.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/iperf-2.0.4-1.fc9

iperf-2.0.4-1.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/iperf-2.0.4-1.fc10

iperf-2.0.4-1.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.

iperf-2.0.4-1.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.