SSH Tunnel dies after opening
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.4k
- Forks
- 993
- Avg merge
- 9d 21h
- Merged PRs (30d)
- 1
Description
I think I may just not be doing this correctly using ForwardedPortDynamic, I start the client and then open the tunnel and it closes after two seconds, the only way I can keep it open is by running a while loop and setting the value false if the port closes, but that causes high cpu usage, trying to figure out how to keep the tunnel open without the crazy high cpu usage
Contributor guide
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
Start by reproducing the reported behavior with ForwardedPortDynamic: open the tunnel and observe whether it closes after two seconds. Compare this with the while-loop workaround and investigate how the tunnel lifecycle is intended to be kept open without busy-waiting. Done means the tunnel remains open without excessive CPU usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100