iperf --dualtest - no check if both servers started
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 59
- Forks
- 27
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 5
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Python entry point that handles the --dualtest option and starts the two socket connections. Reproduce the one-sided connection scenario, then verify that startup detects a missing socket and raises an exception before producing the final report; add or update a focused test if the existing test layout identifies one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100