Confusion regarding extra-listen-port and udp-port

[christaikobo]

I am having a hard time understanding these 2 options, it seems to me from the description provided udp-port should be for server while extra-listen-port should be for client, not the other way around.

For example, if a shadowsocks server doesn't use SIP003u, it will have a UDP port for raw shadowsocks protocol and a client using wss-proxy should specify the port via udp-port.

As for a SIP003u server, it should provide additional UDP port on extra-listen-port for raw shadowsocks protocol so clients without SIP003u can connect to.

Also I am generally confused as to what these 2 options do, I assume they are for client/server with raw shadowsocks protocol? Or are they for client/server with compatible SIP003 plugin like v2ray-plugin? I tried various combination of configs and am not able to make it work.

Anyway also want to say thank you, this plugin is pretty useful as it is already!

[liudongmiao]

It's possible to make shadowsocks-libev udp over tcp without SIP003u. However, it requires more shadowsocks client / server / plugin processes without these options.

However, as shadowsocks-libev was removed in OpenWrt, there two options should be useless.

[christaikobo]

Hey can you give me some hints on how to achieve that? I have got an old R6220 that is only capable of shadowsocks-libev, so I am pretty interested.

[liudongmiao]

The packets that ss local sends to the ss server are identical to those it sends to SS_LOCAL_PORT with SIP003 plugin. Then another ss local without SIP003 plugin can connect to SS_LOCAL_PORT directly. The option extra-listen-port of wss-proxy-client is a stable SS_LOCAL_PORT.

For udp-port, it's similar. However, just use shadowsocks-rust which supports SIP003u.

Consider cipher none (shadowsocks/shadowsocks-libev#2993) with https.

[christaikobo]

Just to be clear:

if I have a sslocal WITH wss-proxy plugin, and I use extra-listen-port=8000 in plugin_opts, then this sslocal will listen on UDP port 8000, which serves as a ssserver without plugin? A secondary sslocal WITHOUT any plugin is able to connect to first sslocal using UDP port 8000?

Basically a daisy chain of shadowsocks, I guess.

[liudongmiao]

wss-proxy-client would offer service on TCP and UDP port extra-listen-port (there is no listen on UDP), acts as SS_LOCAL_PORT in SIP003 and SIP003u.

I don't use OpenWrt anymore, so just try it. However, these options are implemented for shadowsocs-libev, and I have use UDP over TCP on mobile phone.

Please note, I don't opensource nginx patch with websocket over http/2 (RFC 8441)and http/3 (RFC 9220) yet.

[christaikobo]

Alright, thanks for all the tips, and again, appreciate the plugin you have developed! Have a nice day!