DNS请求经过NaiveProxy协议UoT代理报错context deadline exceeded

[yobarerukoto]

操作系统

Linux

系统版本

Fedora 43

安装类型

sing-box 原始命令行程序

如果您使用图形客户端程序，请提供该程序版本。

No response

版本

sing-box version 1.13.4

Environment: go1.25.8 linux/amd64
Tags: with_gvisor,with_quic,with_dhcp,with_wireguard,with_utls,with_acme,with_clash_api,with_tailscale,with_ccm,with_ocm,with_naive_outbound,badlinkname,tfogo_checklinkname0,with_musl
Revision: d09182614c7778c1e0f51d990635c5d4249c437e
CGO: enabled

描述

Naive出站代理的DNS请求会报错exchange4: context deadline exceeded | exchange6: context deadline exceeded，使用tcp类型的DNS服务器或trojan协议都正常，最小复现的配置文件都在同一台机器上跑过，可排除网络质量问题。

客户端配置

{
  "log": {
    "level": "trace",
    "output": "client.log",
    "timestamp": true
  },
  "dns": {
    "servers": [
      {
        "type": "udp",
        "tag": "google",
        "detour": "proxy",
        "server": "8.8.8.8"
      }
    ]
  },
  "inbounds": [
    {
      "type": "socks",
      "listen": "127.0.0.1",
      "listen_port": 1080
    }
  ],
  "outbounds": [
    {
      "type": "naive",
      "tag": "proxy",
      "server": "127.0.0.1",
      "server_port": 9443,
      "username": "username",
      "password": "password",
      "udp_over_tcp": true,
      "tls": {
        "enabled": true,
        "server_name": "example.com"
      }
    }
  ],
  "route": {
    "rules": [
      {
        "action": "resolve",
        "server": "google"
      },
      {
        "ip_is_private": false,
        "outbound": "proxy"
      }
    ]
  }
}

服务端配置

{
  "log": {
    "level": "trace",
    "output": "server.log",
    "timestamp": true
  },
  "inbounds": [
    {
      "type": "naive",
      "listen": "::",
      "listen_port": 9443,
      "users": [
        {
          "Username": "username",
          "Password": "password"
        }
      ],
      "tls": {
        "enabled": true,
        "server_name": "example.com",
        "certificate_path": "/var/ssl/example.com/cert.pem",
        "key_path": "/var/ssl/example.com/cert.key"
      }
    }
  ],
  "outbounds": [
    {
      "type": "direct",
      "tag": "direct"
    }
  ]
}

重现方式

使用如上配置，执行以下命令：

https_proxy=socks5h://127.0.0.1:1080 curl https://google.com

此时非常慢，但能通，然后换个网站

https_proxy=socks5h://127.0.0.1:1080 curl https://bing.com

此时请求会失败，之后所有解析都会失败，都报错exchange4: context deadline exceeded | exchange6: context deadline exceeded

日志

客户端日志：
+0000 2026-04-01 14:14:09 TRACE initialize networkmanager
+0000 2026-04-01 14:14:09 INFO network: updated default interface ens18, index 2
+0000 2026-04-01 14:14:09 TRACE initialize networkmanager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE initialize transportmanager
+0000 2026-04-01 14:14:09 TRACE initialize transportmanager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE initialize router
+0000 2026-04-01 14:14:09 TRACE initialize router completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE initialize connectionmanager
+0000 2026-04-01 14:14:09 TRACE initialize connectionmanager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE initialize router
+0000 2026-04-01 14:14:09 TRACE initialize router completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE initialize manager
+0000 2026-04-01 14:14:09 TRACE outbound: initialize outbound/naive[proxy]
+0000 2026-04-01 14:14:09 TRACE outbound: initialize outbound/naive[proxy] completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE initialize manager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE initialize manager
+0000 2026-04-01 14:14:09 TRACE inbound: initialize inbound/socks[0]
+0000 2026-04-01 14:14:09 TRACE inbound: initialize inbound/socks[0] completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE initialize manager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE initialize manager
+0000 2026-04-01 14:14:09 TRACE initialize manager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE initialize manager
+0000 2026-04-01 14:14:09 TRACE initialize manager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE start manager
+0000 2026-04-01 14:14:09 TRACE outbound: start outbound/naive[proxy]
+0000 2026-04-01 14:14:09 INFO outbound/naive[proxy]: NaiveProxy started, version: 143.0.7499.109
+0000 2026-04-01 14:14:09 TRACE outbound: start outbound/naive[proxy] completed (0.02s)
+0000 2026-04-01 14:14:09 TRACE start manager completed (0.02s)
+0000 2026-04-01 14:14:09 TRACE start transportmanager
+0000 2026-04-01 14:14:09 TRACE start transportmanager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE start router
+0000 2026-04-01 14:14:09 TRACE start router completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE start networkmanager
+0000 2026-04-01 14:14:09 TRACE start networkmanager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE start connectionmanager
+0000 2026-04-01 14:14:09 TRACE start connectionmanager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE start router
+0000 2026-04-01 14:14:09 TRACE start router completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE start manager
+0000 2026-04-01 14:14:09 TRACE inbound: start inbound/socks[0]
+0000 2026-04-01 14:14:09 INFO inbound/socks[0]: tcp server started at 127.0.0.1:1080
+0000 2026-04-01 14:14:09 TRACE inbound: start inbound/socks[0] completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE start manager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE start manager
+0000 2026-04-01 14:14:09 TRACE start manager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE start manager
+0000 2026-04-01 14:14:09 TRACE start manager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE post-start manager
+0000 2026-04-01 14:14:09 TRACE outbound: post-start outbound/naive[proxy]
+0000 2026-04-01 14:14:09 TRACE outbound: post-start outbound/naive[proxy] completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE post-start manager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE post-start networkmanager
+0000 2026-04-01 14:14:09 TRACE post-start networkmanager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE post-start transportmanager
+0000 2026-04-01 14:14:09 TRACE post-start transportmanager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE post-start router
+0000 2026-04-01 14:14:09 TRACE post-start router completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE post-start connectionmanager
+0000 2026-04-01 14:14:09 TRACE post-start connectionmanager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE post-start router
+0000 2026-04-01 14:14:09 TRACE post-start router completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE post-start manager
+0000 2026-04-01 14:14:09 TRACE inbound: post-start inbound/socks[0]
+0000 2026-04-01 14:14:09 TRACE inbound: post-start inbound/socks[0] completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE post-start manager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE post-start manager
+0000 2026-04-01 14:14:09 TRACE post-start manager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE post-start manager
+0000 2026-04-01 14:14:09 TRACE post-start manager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE finish-start networkmanager
+0000 2026-04-01 14:14:09 TRACE finish-start networkmanager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE finish-start transportmanager
+0000 2026-04-01 14:14:09 TRACE finish-start transportmanager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE finish-start router
+0000 2026-04-01 14:14:09 TRACE finish-start router completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE finish-start connectionmanager
+0000 2026-04-01 14:14:09 TRACE finish-start connectionmanager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE finish-start router
+0000 2026-04-01 14:14:09 TRACE finish-start router completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE finish-start manager
+0000 2026-04-01 14:14:09 TRACE outbound: finish-start outbound/naive[proxy]
+0000 2026-04-01 14:14:09 TRACE outbound: finish-start outbound/naive[proxy] completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE finish-start manager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE finish-start manager
+0000 2026-04-01 14:14:09 TRACE inbound: finish-start inbound/socks[0]
+0000 2026-04-01 14:14:09 TRACE inbound: finish-start inbound/socks[0] completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE finish-start manager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE finish-start manager
+0000 2026-04-01 14:14:09 TRACE finish-start manager completed (0.00s)
+0000 2026-04-01 14:14:09 TRACE finish-start manager
+0000 2026-04-01 14:14:09 TRACE finish-start manager completed (0.00s)
+0000 2026-04-01 14:14:09 INFO sing-box started (0.02s)
+0000 2026-04-01 14:14:12 INFO [3923543703 0ms] inbound/socks[0]: inbound connection from 127.0.0.1:48948
+0000 2026-04-01 14:14:12 INFO [3923543703 0ms] inbound/socks[0]: inbound connection to google.com:443
+0000 2026-04-01 14:14:12 DEBUG [3923543703 0ms] router: match[0] => resolve(google)
+0000 2026-04-01 14:14:12 DEBUG [3923543703 0ms] dns: lookup domain google.com
+0000 2026-04-01 14:14:12 INFO [3923543703 0ms] outbound/naive[proxy]: outbound UoT packet connection to 8.8.8.8:53
+0000 2026-04-01 14:14:12 DEBUG outbound/naive[proxy]: open UDP connection to [2001:4860:4860::8888]:443
+0000 2026-04-01 14:14:12 DEBUG outbound/naive[proxy]: open TCP connection to 127.0.0.1:9443
+0000 2026-04-01 14:14:12 DEBUG [3923543703 5ms] outbound/naive[proxy]: response received, protocol: h2, status: 200
+0000 2026-04-01 14:14:12 DEBUG [3923543703 9ms] dns: exchanged google.com NOERROR 154
+0000 2026-04-01 14:14:12 INFO [3923543703 9ms] dns: exchanged AAAA google.com. 154 IN AAAA 2404:6800:4003:c11::64
+0000 2026-04-01 14:14:12 INFO [3923543703 9ms] dns: exchanged AAAA google.com. 154 IN AAAA 2404:6800:4003:c11::66
+0000 2026-04-01 14:14:12 INFO [3923543703 9ms] dns: exchanged AAAA google.com. 154 IN AAAA 2404:6800:4003:c11::8b
+0000 2026-04-01 14:14:12 INFO [3923543703 9ms] dns: exchanged AAAA google.com. 154 IN AAAA 2404:6800:4003:c11::71
+0000 2026-04-01 14:14:22 INFO [3923543703 10.1s] dns: lookup succeed for google.com: 2404:6800:4003:c11::64 2404:6800:4003:c11::66 2404:6800:4003:c11::8b 2404:6800:4003:c11::71
+0000 2026-04-01 14:14:22 DEBUG [3923543703 10.1s] router: resolved [2404:6800:4003:c11::64 2404:6800:4003:c11::66 2404:6800:4003:c11::8b 2404:6800:4003:c11::71]
+0000 2026-04-01 14:14:22 DEBUG [3923543703 10.1s] router: match[1] => route(proxy)
+0000 2026-04-01 14:14:22 INFO [3923543703 10.1s] outbound/naive[proxy]: outbound connection to [2404:6800:4003:c11::64]:443
+0000 2026-04-01 14:14:22 DEBUG [3923543703 10.1s] outbound/naive[proxy]: response received, protocol: h2, status: 200
+0000 2026-04-01 14:14:22 DEBUG [3923543703 10.3s] connection: connection upload finished
+0000 2026-04-01 14:14:22 TRACE [3923543703 10.3s] connection: connection download closed
+0000 2026-04-01 14:14:22 DEBUG [3923543703 10.3s] outbound/naive[proxy]: stream canceled
+0000 2026-04-01 14:14:27 INFO [517602838 0ms] inbound/socks[0]: inbound connection from 127.0.0.1:38196
+0000 2026-04-01 14:14:27 INFO [517602838 0ms] inbound/socks[0]: inbound connection to bing.com:443
+0000 2026-04-01 14:14:27 DEBUG [517602838 0ms] router: match[0] => resolve(google)
+0000 2026-04-01 14:14:27 DEBUG [517602838 0ms] dns: lookup domain bing.com
+0000 2026-04-01 14:14:37 ERROR [517602838 10.0s] dns: lookup failed for bing.com: (exchange4: context deadline exceeded | exchange6: context deadline exceeded)
+0000 2026-04-01 14:14:37 DEBUG [517602838 10.0s] router: connection closed: lookup bing.com: (exchange4: context deadline exceeded | exchange6: context deadline exceeded)
+0000 2026-04-01 14:14:41 TRACE close service
+0000 2026-04-01 14:14:41 TRACE close service completed (0.00s)
+0000 2026-04-01 14:14:41 TRACE close endpoint
+0000 2026-04-01 14:14:41 TRACE close endpoint completed (0.00s)
+0000 2026-04-01 14:14:41 TRACE close inbound
+0000 2026-04-01 14:14:41 TRACE inbound: close inbound/socks[0]
+0000 2026-04-01 14:14:41 TRACE inbound: close inbound/socks[0] completed (0.00s)
+0000 2026-04-01 14:14:41 TRACE close inbound completed (0.00s)
+0000 2026-04-01 14:14:41 TRACE close outbound
+0000 2026-04-01 14:14:41 TRACE outbound: close outbound/naive[proxy]
+0000 2026-04-01 14:14:41 WARN [3923543703 29.4s] outbound/naive[proxy]: stream failed: aborted
+0000 2026-04-01 14:14:41 TRACE outbound: close outbound/naive[proxy] completed (0.00s)
+0000 2026-04-01 14:14:41 TRACE close outbound completed (0.00s)
+0000 2026-04-01 14:14:41 TRACE close router
+0000 2026-04-01 14:14:41 TRACE close router completed (0.00s)
+0000 2026-04-01 14:14:41 TRACE close connection
+0000 2026-04-01 14:14:41 TRACE close connection completed (0.00s)
+0000 2026-04-01 14:14:41 TRACE close dns-router
+0000 2026-04-01 14:14:41 TRACE close dns-router completed (0.00s)
+0000 2026-04-01 14:14:41 TRACE close dns-transport
+0000 2026-04-01 14:14:41 TRACE close dns-transport completed (0.00s)
+0000 2026-04-01 14:14:41 TRACE close network
+0000 2026-04-01 14:14:41 TRACE close network completed (0.00s)
+0000 2026-04-01 14:14:41 TRACE close logger

服务端日志：
+0000 2026-04-01 14:13:59 TRACE initialize networkmanager
+0000 2026-04-01 14:13:59 INFO network: updated default interface ens18, index 2
+0000 2026-04-01 14:13:59 TRACE initialize networkmanager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE initialize transportmanager
+0000 2026-04-01 14:13:59 TRACE initialize transportmanager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE initialize router
+0000 2026-04-01 14:13:59 TRACE initialize router completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE initialize connectionmanager
+0000 2026-04-01 14:13:59 TRACE initialize connectionmanager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE initialize router
+0000 2026-04-01 14:13:59 TRACE initialize router completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE initialize manager
+0000 2026-04-01 14:13:59 TRACE outbound: initialize outbound/direct[direct]
+0000 2026-04-01 14:13:59 TRACE outbound: initialize outbound/direct[direct] completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE initialize manager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE initialize manager
+0000 2026-04-01 14:13:59 TRACE inbound: initialize inbound/naive[0]
+0000 2026-04-01 14:13:59 TRACE inbound: initialize inbound/naive[0] completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE initialize manager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE initialize manager
+0000 2026-04-01 14:13:59 TRACE initialize manager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE initialize manager
+0000 2026-04-01 14:13:59 TRACE initialize manager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE start manager
+0000 2026-04-01 14:13:59 TRACE start manager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE start transportmanager
+0000 2026-04-01 14:13:59 TRACE start transportmanager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE start router
+0000 2026-04-01 14:13:59 TRACE start router completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE start networkmanager
+0000 2026-04-01 14:13:59 TRACE start networkmanager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE start connectionmanager
+0000 2026-04-01 14:13:59 TRACE start connectionmanager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE start router
+0000 2026-04-01 14:13:59 TRACE start router completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE start manager
+0000 2026-04-01 14:13:59 TRACE inbound: start inbound/naive[0]
+0000 2026-04-01 14:13:59 INFO inbound/naive[0]: tcp server started at [::]:9443
+0000 2026-04-01 14:13:59 INFO inbound/naive[0]: udp server started at [::]:9443
+0000 2026-04-01 14:13:59 TRACE inbound: start inbound/naive[0] completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE start manager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE start manager
+0000 2026-04-01 14:13:59 TRACE start manager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE start manager
+0000 2026-04-01 14:13:59 TRACE start manager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE post-start manager
+0000 2026-04-01 14:13:59 TRACE outbound: post-start outbound/direct[direct]
+0000 2026-04-01 14:13:59 TRACE outbound: post-start outbound/direct[direct] completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE post-start manager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE post-start networkmanager
+0000 2026-04-01 14:13:59 TRACE post-start networkmanager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE post-start transportmanager
+0000 2026-04-01 14:13:59 TRACE post-start transportmanager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE post-start router
+0000 2026-04-01 14:13:59 TRACE post-start router completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE post-start connectionmanager
+0000 2026-04-01 14:13:59 TRACE post-start connectionmanager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE post-start router
+0000 2026-04-01 14:13:59 TRACE post-start router completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE post-start manager
+0000 2026-04-01 14:13:59 TRACE inbound: post-start inbound/naive[0]
+0000 2026-04-01 14:13:59 TRACE inbound: post-start inbound/naive[0] completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE post-start manager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE post-start manager
+0000 2026-04-01 14:13:59 TRACE post-start manager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE post-start manager
+0000 2026-04-01 14:13:59 TRACE post-start manager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE finish-start networkmanager
+0000 2026-04-01 14:13:59 TRACE finish-start networkmanager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE finish-start transportmanager
+0000 2026-04-01 14:13:59 TRACE finish-start transportmanager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE finish-start router
+0000 2026-04-01 14:13:59 TRACE finish-start router completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE finish-start connectionmanager
+0000 2026-04-01 14:13:59 TRACE finish-start connectionmanager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE finish-start router
+0000 2026-04-01 14:13:59 TRACE finish-start router completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE finish-start manager
+0000 2026-04-01 14:13:59 TRACE outbound: finish-start outbound/direct[direct]
+0000 2026-04-01 14:13:59 TRACE outbound: finish-start outbound/direct[direct] completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE finish-start manager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE finish-start manager
+0000 2026-04-01 14:13:59 TRACE inbound: finish-start inbound/naive[0]
+0000 2026-04-01 14:13:59 TRACE inbound: finish-start inbound/naive[0] completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE finish-start manager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE finish-start manager
+0000 2026-04-01 14:13:59 TRACE finish-start manager completed (0.00s)
+0000 2026-04-01 14:13:59 TRACE finish-start manager
+0000 2026-04-01 14:13:59 TRACE finish-start manager completed (0.00s)
+0000 2026-04-01 14:13:59 INFO sing-box started (0.00s)
+0000 2026-04-01 14:14:12 INFO [3111522531 0ms] inbound/naive[0]: [username] inbound connection from 127.0.0.1:40190
+0000 2026-04-01 14:14:12 INFO [3111522531 0ms] inbound/naive[0]: [username] inbound connection to sp.v2.udp-over-tcp.arpa:0
+0000 2026-04-01 14:14:12 INFO [3111522531 0ms] inbound/naive[0]: inbound UoT connect connection to 8.8.8.8:53
+0000 2026-04-01 14:14:12 INFO [3111522531 0ms] outbound/direct[direct]: outbound packet connection
+0000 2026-04-01 14:14:22 INFO [2643038283 0ms] inbound/naive[0]: [username] inbound connection from 127.0.0.1:40190
+0000 2026-04-01 14:14:22 INFO [2643038283 0ms] inbound/naive[0]: [username] inbound connection to [2404:6800:4003:c11::64]:443
+0000 2026-04-01 14:14:22 INFO [2643038283 0ms] outbound/direct[direct]: outbound connection to [2404:6800:4003:c11::64]:443
+0000 2026-04-01 14:14:22 TRACE [2643038283 26ms] connection: connection download closed
+0000 2026-04-01 14:14:22 DEBUG [2643038283 26ms] connection: connection upload finished
+0000 2026-04-01 14:14:41 TRACE [3111522531 29.4s] connection: packet upload closed
+0000 2026-04-01 14:14:41 TRACE [3111522531 29.4s] connection: packet download closed
+0000 2026-04-01 14:14:56 TRACE close service
+0000 2026-04-01 14:14:56 TRACE close service completed (0.00s)
+0000 2026-04-01 14:14:56 TRACE close endpoint
+0000 2026-04-01 14:14:56 TRACE close endpoint completed (0.00s)
+0000 2026-04-01 14:14:56 TRACE close inbound
+0000 2026-04-01 14:14:56 TRACE inbound: close inbound/naive[0]
+0000 2026-04-01 14:14:56 TRACE inbound: close inbound/naive[0] completed (0.01s)
+0000 2026-04-01 14:14:56 TRACE close inbound completed (0.01s)
+0000 2026-04-01 14:14:56 TRACE close outbound
+0000 2026-04-01 14:14:56 TRACE close outbound completed (0.00s)
+0000 2026-04-01 14:14:56 TRACE close router
+0000 2026-04-01 14:14:56 TRACE close router completed (0.00s)
+0000 2026-04-01 14:14:56 TRACE close connection
+0000 2026-04-01 14:14:56 TRACE close connection completed (0.00s)
+0000 2026-04-01 14:14:56 TRACE close dns-router
+0000 2026-04-01 14:14:56 TRACE close dns-router completed (0.00s)
+0000 2026-04-01 14:14:56 TRACE close dns-transport
+0000 2026-04-01 14:14:56 TRACE close dns-transport completed (0.00s)
+0000 2026-04-01 14:14:56 TRACE close network
+0000 2026-04-01 14:14:56 TRACE close network completed (0.00s)
+0000 2026-04-01 14:14:56 TRACE close logger

支持我们

• 我已经 赞助

完整性要求

• 我保证阅读了文档，了解所有我编写的配置文件项的含义，而不是大量堆砌看似有用的选项或默认值。
• 我保证提供了可以在本地重现该问题的服务器、客户端配置文件与流程，而不是一个脱敏的复杂客户端配置文件。
• 我保证提供了可用于重现我报告的错误的最简配置，而不是依赖远程服务器、TUN、图形界面客户端或者其他闭源软件。
• 我保证提供了完整的配置文件与日志，而不是出于对自身智力的自信而仅提供了部分认为有用的部分。

[yobarerukoto]

客户端日志里面发现一个很奇怪的地方

+0000 2026-04-01 14:14:12 INFO [3923543703 0ms] outbound/naive[proxy]: outbound UoT packet connection to 8.8.8.8:53
+0000 2026-04-01 14:14:12 DEBUG outbound/naive[proxy]: open UDP connection to [2001:4860:4860::8888]:443

我的客户端配置中只有用IP写的8.8.8.8的服务器，但这个地方不知道为何，识别到要发往8.8.8.8的UoT请求时，下一行出现一个发往2001:4860:4860::8888的UDP请求，这是dns.google的ipv6地址，而且第一次虽慢但成功的请求，也只解析出来了ipv6地址，没看到ipv4的结果。我试了下在resolve动作里面加上"strategy" : "ipv4_only"就一切正常，看来确实跟ipv6有点关系，我可以确认我的网络环境ipv6是正常的，同样的配置，同样是sing-box私有的UoT协议，换成shadowsocks也没问题，只有naive有这个问题