Skip to content

Conversation

@matthew-on-git
Copy link

comment out corresponding (output=) line on 17 or 20

I'm testing this in our environment. Manual iperf testing showed that I needed to use at least 10 parallel tests for over 30-40 seconds to get a max bandwidth expected.

The modifications I made to the grep line seemed to work as it only grabs the SUM lines of the iperf output. Not 100% confident in the tests just yet. Maybe someone can confirm my changes.

comment out corresponding (output=) line on 17 or 20
@rkagerer
Copy link
Owner

rkagerer commented Sep 19, 2017

Hey matthewmdn, thanks for submitting to my humble little Github archive!

Honestly, I haven't touched this script in ages, and unfortunately don't have the capacity at the moment to do any additional testing or make updates aside from very trivial ones.

Hopefully folks interested in iperf3 will notice your pull request and go there. If you want me to surface this information better, let me know.

Eventually if/when I get around to updating this in my own environment I'll do some testing and look at reviewing and integrating your enhancements.

Again, thanks so much, I'm sure the insight you've shared will be very helpful to someone (and myself, when the time comes)!

@matthew-on-git
Copy link
Author

matthew-on-git commented Sep 20, 2017 via email

@K0NCTANT1N
Copy link

PRTG Network Monitor 17.3.32.2478+ the information is not displayed, although the script is running and the check is in progress.

@K0NCTANT1N
Copy link

PRTG answer: Failed to read paessh command from shell (1). Reason: read_paessh timeout

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants