There is a possibility that the iperf server collects and outputs the data with a delay larger than 5 seconds that we are giving it now. Please try replacing line 177 in benchmark.py: self.get_results() with gobject.timeout_add(10000, self.get_results). This will wait an extra 10 seconds before asking for iperf's output.
If the extra waiting doesn't work, please try manually running iperf -s -xS -yC on the computer where epoptes is running and iperf -c server -r -t 7 on a client. This is equivalent to an 20sec test via epoptes. Thanks for testing -- You received this bug notification because you are a member of Epoptes Developers, which is subscribed to Epoptes. https://bugs.launchpad.net/bugs/1376678 Title: Network performance not working Status in Epoptes: New Bug description: when trying to run a benchmark on the network I get: bind failed: Address already in use Killing the iperf server Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/epoptes/ui/benchmark.py", line 177, in update_time_left self.get_results() File "/usr/lib/python2.7/dist-packages/epoptes/ui/benchmark.py", line 204, in get_results client = line[3] IndexError: list index out of range To manage notifications about this bug go to: https://bugs.launchpad.net/epoptes/+bug/1376678/+subscriptions -- Mailing list: https://launchpad.net/~epoptes Post to : [email protected] Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
