Skip to content
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

Port Forwarding via ShadowSocks bug #439

Closed
philinp opened this issue Mar 29, 2024 · 1 comment
Closed

Port Forwarding via ShadowSocks bug #439

philinp opened this issue Mar 29, 2024 · 1 comment

Comments

@philinp
Copy link

philinp commented Mar 29, 2024

Test#1 (connecting to ssh via socks4a) is OK:
./gost -L socks4a://:1001
./gost -L tcp://:1002/127.0.0.1:22 -F socks4a://127.0.0.1:1001

# telnet 127.0.0.1 1002
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
SSH-2.0-OpenSSH_9.2p1

Test#2 (connecting to ssh via socks4a via shadowsocks) is failed:
./gost -L ss://:1003
./gost -L socks4a://:1004 -F ss://127.0.0.1:1003
./gost -L tcp://:1005/127.0.0.1:22 -F socks4a://127.0.0.1:1004

# telnet 127.0.0.1 1005
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.

The problem is that the ssh banner doesn't show up in the Test#2.

PS:
Original go-shadowsocks2 is working OK and changing ss:// to kcp:// is working OK too.

Tested version:

# ./gost -V
gost v3.0.0-nightly.20240201 (go1.21.6 linux/386)
@ginuerzh
Copy link
Member

You should add the nodelay option for ss client:

./gost -L socks4a://:1004 -F ss://127.0.0.1:1003?nodelay=true

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

2 participants