Skip to content
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

UoT is rejected on server host with a "global UoT not supported since sing-box v1.7.0" error #2668

Closed
4 of 5 tasks
arinc9 opened this issue Mar 3, 2025 · 4 comments · May be fixed by #2686
Closed
4 of 5 tasks

UoT is rejected on server host with a "global UoT not supported since sing-box v1.7.0" error #2668

arinc9 opened this issue Mar 3, 2025 · 4 comments · May be fixed by #2686

Comments

@arinc9
Copy link

arinc9 commented Mar 3, 2025

Operating system

Linux

System version

Debian 13

Installation type

Original sing-box Command Line

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

No response

Version

main branch

Description

We use MPTCP to proxy client's TCP and UDP traffic. So we need to be able to send UDP traffic in TCP. With the current configuration I have, UoT is rejected on the server host with a "global UoT not supported since sing-box v1.7.0" error.

Reproduction

Client:

{
  "inbounds": [
    {
      "type": "tproxy",
      "listen": "127.0.0.1",
      "listen_port": 12345
    }
  ],
  "outbounds": [
    {
      "type": "shadowsocks",
      "server": "server",
      "server_port": 12343,
      "method": "none",
      "password": "",
      "udp_over_tcp": {
        "enabled": true
      },
      "tcp_multi_path": true
    }
  ]
}

Server:

{
  "inbounds": [
    {
      "type": "shadowsocks",
      "listen": "::",
      "listen_port": 12343,
      "network": "tcp",
      "tcp_multi_path": true,
      "method": "none",
      "password": ""
    }
  ],
  "outbounds": [
    {
      "type": "direct"
    }
  ]
}

Logs

Client

INFO[2330] [3035214919 0ms] inbound/tproxy[0]: inbound packet connection from 192.168.1.183:41953
INFO[2330] [3035214919 0ms] inbound/tproxy[0]: inbound packet connection to host:1234
INFO[2330] [3035214919 1ms] outbound/shadowsocks[0]: outbound UoT packet connection to host:1234
TRACE[2330] [3035214919 8ms] connection: packet download closed
TRACE[2330] [3035214919 8ms] connection: packet upload closed


Server

INFO[0494] [1900851697 0ms] inbound/shadowsocks[0]: inbound connection from client:34438
INFO[0494] [1900851697 0ms] inbound/shadowsocks[0]: inbound connection to sp.v2.udp-over-tcp.arpa:0
ERROR[0494] [1900851697 0ms] inbound/shadowsocks[0]: process connection from client:34438: global UoT not supported since sing-box v1.7.0.

Supporter

Integrity requirements

  • 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.
  • 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.
  • 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.
  • 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.
@nekohasekai
Copy link
Member

@nekohasekai nekohasekai closed this as not planned Won't fix, can't repro, duplicate, stale Mar 5, 2025
@arinc9
Copy link
Author

arinc9 commented Mar 5, 2025

The only relevant text I see there is below which does not explain anything to what I described here, and it does not present a reason for the rejection of the feature I requested. You've made a bad response.

Migrate multiplex and UoT server to inbound 3

@nekohasekai
Copy link
Member

You have to enable multiplex in inbound for the same.

@arinc9
Copy link
Author

arinc9 commented Mar 5, 2025

What do you mean?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants