-
Notifications
You must be signed in to change notification settings - Fork 166
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
Socks proxy under linux #480
Comments
@alcarinque-istar I see you don't have all the ports opened in their correct protocols. See here for the full list as well as their protocols: https://github.com/moonlight-stream/moonlight-docs/wiki/Setup-Guide#streaming-over-the-internet |
Ok, I did a complete scan, and as you see some ports are indeed closed. But I think those are only opened when a game is running, just guessing. Windows firewall is disabled.
I also tried this program: Sshuttle https://github.com/sshuttle/sshuttle
As you see, it stills seems to be a network problem. Maybe is trying to resolve the hostname using some kind of broadcast that doesn't propagate through the tunnel? |
@alcarinque-istar I'm no expert know this, but I know that some ports are booth TCP AND UDP |
Bump on this! |
@steven200796 I'm not expert into this; I'll probably need @cgutman's help on that bug |
try this |
I am trying to access a Windows 10 server running nvidia-experience app.
My client computer is behind a firewall but I can enter the local network through a ssh tunnel. This is my setup:
| Client PC | --> | Firewall | --> (internet) --> | Ssh Server | --> | Windows PC |
I tried running google-chrome in the client pc with the
google-chrome-stable --proxy-server="socks5://127.0.0.1:54321" --host-resolver-rules="MAP * ~NOTFOUND , EXCLUDE 127.0.0.1"
command line, but when trying to pair moonlight says: Pairing to 192.168.... failed.
The console gives:
I used proxychains to run the old java app and I can pair, but it gives me this error in console:
I checked the ports from the ssh server using nmap:
Is there anything else I could try?
The text was updated successfully, but these errors were encountered: