Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iperf --dualtest - no check if both servers started #211

Open
greg-latuszek opened this issue Sep 27, 2019 · 0 comments
Open

iperf --dualtest - no check if both servers started #211

greg-latuszek opened this issue Sep 27, 2019 · 0 comments

Comments

@greg-latuszek
Copy link
Collaborator

iperf may be run in simultaneous downlink/uplink mode using --dualtest option

In such case client side starts iperf server process as well and server side establishes second client socket.

If there is communication problem (wrong routing, blocking proxy, etc) only one socket is established on both sides. Command seems to run ok but final report for the other direction will be missing.

We should check (at command startup) if both sockets have been established for --dualtest and if not we quickly raise exception.

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

No branches or pull requests

1 participant