Shadowsocks tcp_only and udp_only

[knano]

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:

SS-TCP Listener  --->  Forwarder1 (may only support tcp)  --->  Internet
SS-UDP Listener  --->  Forwarder2 (support udp)  --->  Internet

Thanks.

[nadoo]

Hi @knano , may I ask why don't you use 2 instances to achieve your goal?
glider -verbose -listen :8443 -forward ss://forwarder1(may only support tcp)
glider -verbose -listen :8444 -forward ss://forwarder2(support udp)

[knano]

Hi @knano , may I ask why don't you use 2 instances to achieve your goal?
glider -verbose -listen :8443 -forward ss://forwarder1(may only support tcp)
glider -verbose -listen :8444 -forward ss://forwarder2(support udp)

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:

glider -listen ss-tcp-only://method:[email protected]:8388 -forward vmess://forwarder1(may not be so friendly to udp)
glider -listen ss-udp-only://method:[email protected]:8388 -forward ss://forwarder2(support udp, and even Full cone NAT)

Then, users can use any shadowsocks clients to connect to the server above, and enjoy both tcp and udp.