The client will not use multiplex when the outbound type is shadowsocks even if the multiplex is enabled

[h0NponJR]

Operating system

Linux

System version

Ubuntu 24.04 LTS

Installation type

Original sing-box Command Line

If you are using a graphical client, please provide the version of the client.

no

Version

sing-box version 1.10.0-alpha.20

Description

The client will not use multiplex when the outbound type is shadowsocks even if the multiplex is enabled

Reproduction

Server configuration

{
  "inbounds": [
    {
      "type": "shadowsocks",
      "tag": "ss-in",
      "listen": "::",
      "listen_port": 8080,
      "sniff": true,
      "sniff_override_destination": true,
      "network": "tcp",
      "method": "2022-blake3-aes-256-gcm",
      "password": "xxx",
      "multiplex": {
        "enabled": true
      }
    }
  ]
}

Client configuration

{
  "outbounds": [
   {
      "type": "shadowsocks",
      "tag": "ss-out",
      "server": "xxx",
      "server_port": 8080,
      "detour": "Tunnel",
      "multiplex": {
        "enabled": true,
        "max_connections": 4,
        "min_streams": 4
      },
      "method": "2022-blake3-aes-256-gcm",
      "password": "xxx",
      "udp_over_tcp": {
        "enabled": true,
        "version": 2
      }
    }
  ]
}

Logs

When I connect to the server using sing-box, the logs on the server show that it doesn't use multiplex 

+0000 2024-07-12 12:15:42 INFO [2409805482 0ms] inbound/shadowsocks[ss-in]: inbound connection from xxx.xxx.xxx.xxx:18067
+0000 2024-07-12 12:15:42 INFO [3895130731 8ms] inbound/shadowsocks[ss-in]: inbound connection to xxx.xxx.xxx.xxx:443

But when I use Clash Meta, the logs on the server show that it uses multiplex

+0000 2024-07-12 12:07:10 INFO [851908838 0ms] inbound/shadowsocks[ss-in]: inbound connection to sp.mux.sing-box.arpa:444
+0000 2024-07-12 12:07:10 INFO [1971490266 0ms] inbound/shadowsocks[ss-in]: inbound multiplex connection to xxx.xxx.xxx.xxx:8080
+0000 2024-07-12 12:07:10 INFO [2802879542 0ms] inbound/shadowsocks[ss-in]: inbound multiplex connection to xxx.xxx.xxx.xxx:8080

### Supporter

- [ ] I am a [sponsor](https://github.com/sponsors/nekohasekai/)

### Integrity requirements

- [X] I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
- [X] I confirm that I have provided the server and client configuration files and process that can be reproduced locally, instead of a complicated client configuration file that has been stripped of sensitive data.
- [X] I confirm that I have provided the simplest configuration that can be used to reproduce the error I reported, instead of depending on remote servers, TUN, graphical interface clients, or other closed-source software.
- [X] I confirm that I have provided the complete configuration files and logs, rather than just providing parts I think are useful out of confidence in my own intelligence.

[yanhao98]

udp_over_tcp

UDP over TCP 配置。

参阅 UDP Over TCP。

与 multiplex 冲突。