-
Notifications
You must be signed in to change notification settings - Fork 402
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
Shadowsocks tcp_only and udp_only #215
Comments
Hi @knano , may I ask why don't you use 2 instances to achieve your goal? |
Hi @nadoo , thanks for your relay. In fact, in my case, I use a "shadowsocks forwarding server" rather than a client. For example, on the server:
Then, users can use any shadowsocks clients to connect to the server above, and enjoy both tcp and udp. |
Currently shadowsocks works on both TCP and UDP by default. Is it possible to add tcp_only and udp_only option?
This may be helpful to separate the TCP and UDP forward chain:
Thanks.
The text was updated successfully, but these errors were encountered: