ssh + tunnell

Open
#13 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
networking

Research direction

No source file or test is named. Start by reproducing the SSH.NET remote port-forward setup and compare the standard .NET HttpListener with websocket-sharp under the same tunnel. Done means identifying which component prevents the websocket connection and documenting a reproducible fix or clear diagnosis.

Written by the indexing model from the issue text.

Description

Is there any reason known why websocket-sharp will not work over a tunnel using ssh and remote port forward.

I've been testing with SSH.NET.

If I use the standard .NET HttpListener all works fine. As soon as I use with websocket-sharp it stops working.

The issue seems very strange and I am having trouble getting any useful debug information.

I think it could either be...

  1. An issue with websocket-sharp and SSH.NET remote port forwarding
  2. An issue with the HttpListener

Debugging and it seems that SSH.NET and the fowarding all connects correctly, which made me think it was something to do with the HttpListener - but this never gets.

Dominant language
C#
Stars
6.1k
Forks
1.7k
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sta/websocket-sharp

All issues in sta/websocket-sharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.