Why plugin only enabled for tcp?

[videni]

do we also need to enable plugin for UDP ? I don't have an use case, I am just curious why plugin is enabled for tcp only currently.

        if self.svr_cfg.mode().enable_tcp() {
            if let Some(plugin_cfg) = self.svr_cfg.plugin() {
                let plugin = Plugin::start(plugin_cfg, self.svr_cfg.addr(), PluginMode::Server)?;
                self.svr_cfg.set_plugin_addr(plugin.local_addr().into());
                vfut.push(
                    async move {
                        match plugin.join().await {
                            Ok(status) => {
                                error!("plugin exited with status: {}", status);
                                Ok(())
                            }
                            Err(err) => {
                                error!("plugin exited with error: {}", err);
                                Err(err)
                            }
                        }
                    }
                    .boxed(),
                );
            }

            let tcp_fut = self.run_tcp_server().boxed();
            vfut.push(tcp_fut);
        }

[zonyitoo]

shadowsocks/shadowsocks-org#28

b. Only TCP traffic is forwarded. For now, there is no plan to support UDP traffic forwarding.

This comment explains why.

[mazzz1y]

@zonyitoo

from explanation:

UDP over TCP expects very poor performance.

I can't confirm that. I agree that udp-over-tcp is not the most optimal way, but it works good. For example with pure Xray-VMess-WebSocket I can use udp voice streaming without any problem.

It will be very good if shadowsocks will add udp support for plugins.

[zonyitoo]

Please post your advices to the SIP003 issue.