My mistake it's fixed in Precise too.
** Changed in: iperf (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1020787
Title:
iperf -s should not dis
Version: 2.0.5-3
This is fixed in Saucy (and looking at the version numbers it's probably
fixed in Quantal+ too).
** Changed in: iperf (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Already reported upstream.
https://sourceforge.net/tracker/?func=detail&aid=1983829&group_id=128336&atid=711371
No idea if/how this can be linked in Launchpad.
** Bug watch added: SourceForge.net Tracker #1983829
http://sourceforge.net/support/tracker.php?aid=1983829
--
You received this bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1020787
Title:
iperf -s should not disconnect after a dualtest
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/i
