Skip to content

usage question #690

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

Open
dstoffel opened this issue Apr 4, 2025 · 1 comment
Open

usage question #690

dstoffel opened this issue Apr 4, 2025 · 1 comment

Comments

@dstoffel
Copy link

dstoffel commented Apr 4, 2025

Hi,

I'm trying to achieve the following and i'm not sure to understand if it is supported or not:

Doing the equivalent of "ssh -R, without SSH ".
Server-A is running SSH, Server-B connect to Server-A using option -R 1080.
This create a listening port (1080) on Server-A which act a a socks proxy, data sent to server-A:1080 go out through Server-B.

Thank you !
Davy

@dstoffel
Copy link
Author

dstoffel commented Apr 4, 2025

I finally found :

server-A:
./gost -L relay+grpc://user:pass@:1080?bind=true
curl --proxy socks5h://127.0.0.1:2222 -v http://test.com

server-B:
./gost -L=rtcp://:2222/127.0.0.1:9999 -F relay+grpc://user:pass@server-A:1080
./gost -L=socks5://:9999

Question, on server-B, can we do this in one command ?

./gost -L=rtcp://:2222/127.0.0.1:9999 -L=socks5://127.0.0.1:9999 -F relay+grpc://user:pass@server-A::1080 is not working (curl: (35) error:0A000126:SSL routines::unexpected eof while reading, nothing relevant in gost output)

Second question, let's assume i do not trust server-B, can i somehow configure the listener of server-A to only allow rtcp://:2222/127.0.0.1:9999 and nothing else ?

thanks,
Davy

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