-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Feature Request: Chain Shadowsocks #904
Comments
You can do this with a tunnel:
|
Could you give me an example of commands to do this? |
Let's say if you have a server running on Local server: sslocal -b '127.0.0.1:1080' -s '100.100.100.101:2345' -m 'aes-128-gcm' -k 'TARGET_SERVER_PWD' Middle server: # Start a sslocal with tunnel protocol, forwarding all data to 100.100.100.200:1234
sslocal -b '100.100.100.101:2345' --protocol tunnel -s '127.0.0.1:8888' -m 'plain' -k '' --forward-addr '100.100.100.200:1234'
# Start a ssserver locally
ssserver -b '127.0.0.1:8888' -m 'plain' -k '' Target server: ssserver -s '100.100.100.200:1234' -m 'aes-128-gcm' -k 'TARGET_SERVER_PWD' BUT. This is slow, because all the middle servers must run both
Some possible choices:
|
Implement port hopping Users in China sometimes report that their ISPs block or throttle persistent UDP connections. However, these restrictions often only apply to the specific port being used. Port hopping can be used as a workaround for this situation. |
Is your feature request related to a problem? Please describe.
I would like to create a chain of shadowsocks servers like proxychains
client - ss server - ss server - ss server - ss server -target
Describe the solution you'd like
Have a chain option in shadowsocks
The text was updated successfully, but these errors were encountered: