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.

Sign up for GitHub

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

Jump to bottom

最新测试版部分协议udp不通 #2364

Closed
4 of 5 tasks
swysgh opened this issue Dec 13, 2024 · 8 comments
Closed
4 of 5 tasks

最新测试版部分协议udp不通 #2364

swysgh opened this issue Dec 13, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@swysgh
Copy link

swysgh commented Dec 13, 2024 •
edited
Loading

操作系统

Linux

系统版本

debian12

安装类型

sing-box 原始命令行程序

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

No response

版本

sing-box version 1.11.0-beta.9

Environment: go1.23.4 linux/amd64
Tags: with_gvisor,with_quic,with_dhcp,with_wireguard,with_ech,with_utls,with_reality_server,with_acme,with_clash_api
Revision: 4d9f2a4801dbd6c29049005eb3dc196b113678ad
CGO: disabled

描述

由于我的claw的wireguard被干扰了，所以我打算使用sing-box中转。但是使用direct中转后发现udp不通，而且回想起之前udp连接dns时也出现断联，部分协议正常。目前测试了ss2022，vless的ws和reality，均不通，换到正式版后就恢复正常了。(direct正常)
由于之前节点的udp都是正常的，突然无法使用，故只作推测，折腾到太晚了，没有在内网进行测试，明天再测试。
对了，我是把sing-box接在软路由前方的，中间的连接协议使用的是socks5。
由于复刻过于简单加上我太困了，配置就先不贴了，如果需要到时候再补

重现方式

使用最新测试版并使用udp连接vless或ss节点

日志

客户端
root@debsmall:/etc/sing-box# journalctl -u sing-box.service --output cat -f
+0800 2024-12-14 02:47:14 INFO [2683459924 0ms] outbound/vless[dyeq-vless]: outbound multiplex packet connection to :0
+0800 2024-12-14 02:47:16 INFO [1364340137 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:37090
+0800 2024-12-14 02:47:16 INFO [1364340137 0ms] inbound/mixed[mixed-in]: inbound packet connection to :0
+0800 2024-12-14 02:47:16 INFO [1364340137 1ms] outbound/vless[dyeq-vless]: outbound multiplex packet connection to :0
+0800 2024-12-14 02:47:16 INFO [39869188 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:37106
+0800 2024-12-14 02:47:16 INFO [39869188 0ms] inbound/mixed[mixed-in]: inbound packet connection to :0
+0800 2024-12-14 02:47:16 INFO [39869188 1ms] outbound/vless[dyeq-vless]: outbound multiplex packet connection to :0
+0800 2024-12-14 02:47:21 INFO [3965882508 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:37112
+0800 2024-12-14 02:47:21 INFO [3965882508 0ms] inbound/mixed[mixed-in]: inbound packet connection to :0
+0800 2024-12-14 02:47:21 INFO [3965882508 1ms] outbound/vless[dyeq-vless]: outbound multiplex packet connection to :0
+0800 2024-12-14 02:47:25 INFO [3122087510 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:54896
+0800 2024-12-14 02:47:25 INFO [3122087510 0ms] inbound/mixed[mixed-in]: inbound packet connection to :0
+0800 2024-12-14 02:47:25 INFO [3122087510 1ms] outbound/vless[dyeq-vless]: outbound multiplex packet connection to :0
+0800 2024-12-14 02:47:27 INFO [409175241 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:54902
+0800 2024-12-14 02:47:27 INFO [409175241 0ms] inbound/mixed[mixed-in]: inbound packet connection to :0
+0800 2024-12-14 02:47:27 INFO [409175241 1ms] outbound/vless[dyeq-vless]: outbound multiplex packet connection to :0
+0800 2024-12-14 02:47:27 INFO [417479643 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:54904
+0800 2024-12-14 02:47:27 INFO [417479643 0ms] inbound/mixed[mixed-in]: inbound packet connection to :0
+0800 2024-12-14 02:47:27 INFO [417479643 1ms] outbound/vless[dyeq-vless]: outbound multiplex packet connection to :0
+0800 2024-12-14 02:47:28 INFO [3263958049 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:54912
+0800 2024-12-14 02:47:28 INFO [3263958049 0ms] inbound/mixed[mixed-in]: inbound packet connection to :0
+0800 2024-12-14 02:47:28 INFO [3263958049 1ms] outbound/vless[dyeq-vless]: outbound multiplex packet connection to :0
+0800 2024-12-14 02:47:30 INFO [2241605808 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:32846
+0800 2024-12-14 02:47:30 INFO [2241605808 0ms] inbound/mixed[mixed-in]: inbound connection to 91.108.56.150:443
+0800 2024-12-14 02:47:30 INFO [1000384301 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:32860
+0800 2024-12-14 02:47:30 INFO [1000384301 0ms] inbound/mixed[mixed-in]: inbound connection to 91.108.56.150:80
+0800 2024-12-14 02:47:30 INFO [1000384301 0ms] outbound/vless[dyeq-vless]: outbound multiplex connection to 91.108.56.150:80
+0800 2024-12-14 02:47:30 INFO [2241605808 300ms] outbound/vless[dyeq-vless]: outbound multiplex connection to 91.108.56.150:443
+0800 2024-12-14 02:47:32 INFO [1772054934 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:54922
+0800 2024-12-14 02:47:32 INFO [1772054934 0ms] inbound/mixed[mixed-in]: inbound packet connection to :0
+0800 2024-12-14 02:47:32 INFO [1772054934 1ms] outbound/vless[dyeq-vless]: outbound multiplex packet connection to :0
+0800 2024-12-14 02:47:36 INFO [1123696357 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:32864
+0800 2024-12-14 02:47:36 INFO [1123696357 0ms] inbound/mixed[mixed-in]: inbound connection to 74.125.204.188:5228
+0800 2024-12-14 02:47:36 INFO [1123696357 1ms] outbound/vless[dyeq-vless]: outbound multiplex connection to 74.125.204.188:5228
+0800 2024-12-14 02:47:36 INFO [1058413200 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:32880
+0800 2024-12-14 02:47:36 INFO [1058413200 0ms] inbound/mixed[mixed-in]: inbound connection to 142.250.199.238:443
+0800 2024-12-14 02:47:36 INFO [1058413200 1ms] outbound/vless[dyeq-vless]: outbound multiplex connection to 142.250.199.238:443
+0800 2024-12-14 02:47:37 INFO [712732806 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:42260
+0800 2024-12-14 02:47:37 INFO [712732806 0ms] inbound/mixed[mixed-in]: inbound packet connection to :0
+0800 2024-12-14 02:47:37 INFO [712732806 0ms] outbound/vless[dyeq-vless]: outbound multiplex packet connection to :0
+0800 2024-12-14 02:47:37 INFO [712732806 602ms] outbound/vless[dyeq-vless]: outbound connection to sp.mux.sing-box.arpa:444
+0800 2024-12-14 02:47:39 INFO [3606872061 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:32894
+0800 2024-12-14 02:47:39 INFO [3606872061 0ms] inbound/mixed[mixed-in]: inbound connection to 1.1.1.1:53
+0800 2024-12-14 02:47:39 INFO [902250015 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:32898
+0800 2024-12-14 02:47:39 INFO [902250015 0ms] inbound/mixed[mixed-in]: inbound connection to 54.230.71.45:443
+0800 2024-12-14 02:47:39 INFO [3606872061 0ms] outbound/vless[dyeq-vless]: outbound multiplex connection to 1.1.1.1:53
+0800 2024-12-14 02:47:39 INFO [902250015 0ms] outbound/vless[dyeq-vless]: outbound multiplex connection to 54.230.71.45:443
+0800 2024-12-14 02:47:39 INFO [902250015 143ms] outbound/vless[dyeq-vless]: outbound connection to sp.mux.sing-box.arpa:444
+0800 2024-12-14 02:47:39 INFO [2640303236 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:42264
+0800 2024-12-14 02:47:39 INFO [2640303236 0ms] inbound/mixed[mixed-in]: inbound packet connection to :0
+0800 2024-12-14 02:47:39 INFO [2640303236 1ms] outbound/vless[dyeq-vless]: outbound multiplex packet connection to :0
+0800 2024-12-14 02:47:43 INFO [1782060484 0ms] inbound/mixed[mixed-in]: inbound connection from 192.168.1.2:44318
+0800 2024-12-14 02:47:43 INFO [1782060484 0ms] inbound/mixed[mixed-in]: inbound packet connection to :0
+0800 2024-12-14 02:47:43 INFO [1782060484 0ms] outbound/vless[dyeq-vless]: outbound multiplex packet connection to :0

服务端
root@VM85211:~# journalctl -u sing-box.service --output cat -f
+0800 2024-12-14 02:46:50 INFO [26714359 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:46:50 ERROR [26714359 300ms] router: timeout
+0800 2024-12-14 02:46:53 ERROR [218007648 1m0s] inbound/vless[vless-in]: process multiplex connection from 127.0.0.1:45564: EOF
+0800 2024-12-14 02:46:54 INFO [219285870 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:46:54 ERROR [219285870 301ms] router: timeout
+0800 2024-12-14 02:46:55 INFO [3811799119 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:46:55 ERROR [3811799119 301ms] router: timeout
+0800 2024-12-14 02:46:58 INFO [2981858570 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:46:58 ERROR [2981858570 301ms] router: timeout
+0800 2024-12-14 02:47:01 INFO [2733092097 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:01 INFO [399812685 0ms] inbound/vless[vless-in]: inbound multiplex connection to [2606:4700:300a::6813:c0b0]:443
+0800 2024-12-14 02:47:01 INFO [399812685 0ms] outbound/direct: outbound connection to [2606:4700:300a::6813:c0b0]:443
+0800 2024-12-14 02:47:01 ERROR [2733092097 302ms] router: timeout
+0800 2024-12-14 02:47:02 INFO [2370958216 0ms] inbound/vless[vless-in]: inbound multiplex connection to 149.154.167.222:80
+0800 2024-12-14 02:47:02 INFO [2370958216 0ms] outbound/direct: outbound connection to 149.154.167.222:80
+0800 2024-12-14 02:47:03 INFO [568535950 0ms] inbound/vless[vless-in]: inbound connection from 127.0.0.1:40288
+0800 2024-12-14 02:47:03 INFO [568535950 46ms] inbound/vless[vless-in]: [swysgh] inbound connection to sp.mux.sing-box.arpa:444
+0800 2024-12-14 02:47:03 INFO [122993945 0ms] inbound/vless[vless-in]: inbound multiplex connection to 149.154.167.222:443
+0800 2024-12-14 02:47:03 INFO [122993945 300ms] outbound/direct: outbound connection to 149.154.167.222:443
+0800 2024-12-14 02:47:04 INFO [1005771223 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:04 ERROR [1005771223 301ms] router: timeout
+0800 2024-12-14 02:47:05 INFO [3807911774 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:05 ERROR [3807911774 301ms] router: timeout
+0800 2024-12-14 02:47:06 INFO [2973476302 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:06 ERROR [2973476302 301ms] router: timeout
+0800 2024-12-14 02:47:09 ERROR [442588174 1m20s] inbound/vless[vless-in]: process multiplex connection from 127.0.0.1:45560: EOF
+0800 2024-12-14 02:47:11 INFO [194838554 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:11 ERROR [194838554 301ms] router: timeout
+0800 2024-12-14 02:47:15 INFO [164471630 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:15 ERROR [164471630 300ms] router: timeout
+0800 2024-12-14 02:47:16 INFO [2958595393 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:16 ERROR [2958595393 301ms] router: timeout
+0800 2024-12-14 02:47:17 INFO [3743867539 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:17 ERROR [3743867539 300ms] router: timeout
+0800 2024-12-14 02:47:21 INFO [3179185191 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:21 ERROR [3179185191 301ms] router: timeout
+0800 2024-12-14 02:47:26 INFO [81561089 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:26 ERROR [81561089 301ms] router: timeout
+0800 2024-12-14 02:47:27 INFO [1621808264 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:28 ERROR [1621808264 301ms] router: timeout
+0800 2024-12-14 02:47:29 INFO [3376309149 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:29 ERROR [3376309149 301ms] router: timeout
+0800 2024-12-14 02:47:30 ERROR [2160893901 1m7s] inbound/vless[vless-in]: process multiplex connection from 127.0.0.1:54510: EOF
+0800 2024-12-14 02:47:30 INFO [325761488 0ms] inbound/vless[vless-in]: inbound multiplex connection to 91.108.56.150:80
+0800 2024-12-14 02:47:30 INFO [325761488 1ms] outbound/direct: outbound connection to 91.108.56.150:80
+0800 2024-12-14 02:47:30 INFO [395049902 0ms] inbound/vless[vless-in]: inbound multiplex connection to 91.108.56.150:443
+0800 2024-12-14 02:47:30 INFO [395049902 300ms] outbound/direct: outbound connection to 91.108.56.150:443
+0800 2024-12-14 02:47:31 ERROR [1349470597 1m25s] inbound/vless[vless-in]: process multiplex connection from 127.0.0.1:34632: EOF
+0800 2024-12-14 02:47:31 ERROR [1091106415 1m0s] inbound/vless[vless-in]: process multiplex connection from 127.0.0.1:43410: EOF
+0800 2024-12-14 02:47:32 INFO [1180745607 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:32 ERROR [1180745607 301ms] router: timeout
+0800 2024-12-14 02:47:36 ERROR [2665375505 1m3s] inbound/vless[vless-in]: process multiplex connection from 127.0.0.1:43438: EOF
+0800 2024-12-14 02:47:36 INFO [350470957 0ms] inbound/vless[vless-in]: inbound multiplex connection to 74.125.204.188:5228
+0800 2024-12-14 02:47:36 INFO [350470957 0ms] outbound/direct: outbound connection to 74.125.204.188:5228
+0800 2024-12-14 02:47:36 INFO [3561216337 1ms] inbound/vless[vless-in]: inbound multiplex connection to 142.250.199.238:443
+0800 2024-12-14 02:47:36 INFO [3561216337 1ms] outbound/direct: outbound connection to 142.250.199.238:443
+0800 2024-12-14 02:47:37 INFO [3369521167 0ms] inbound/vless[vless-in]: inbound connection from 127.0.0.1:49542
+0800 2024-12-14 02:47:38 INFO [3369521167 199ms] inbound/vless[vless-in]: [swysgh] inbound connection to sp.mux.sing-box.arpa:444
+0800 2024-12-14 02:47:38 INFO [2297829986 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:38 ERROR [2297829986 301ms] router: timeout
+0800 2024-12-14 02:47:39 INFO [2048807393 0ms] inbound/vless[vless-in]: inbound connection from 127.0.0.1:49548
+0800 2024-12-14 02:47:39 INFO [2048807393 47ms] inbound/vless[vless-in]: [swysgh] inbound connection to sp.mux.sing-box.arpa:444
+0800 2024-12-14 02:47:39 INFO [3818177498 0ms] inbound/vless[vless-in]: inbound multiplex connection to 54.230.71.45:443
+0800 2024-12-14 02:47:39 INFO [3818177498 0ms] outbound/direct: outbound connection to 54.230.71.45:443
+0800 2024-12-14 02:47:39 INFO [3579896787 0ms] inbound/vless[vless-in]: inbound multiplex connection to 1.1.1.1:53
+0800 2024-12-14 02:47:39 INFO [3579896787 37ms] dns: exchanged s.voce.chat CNAME s.voce.chat. 60 IN CNAME d3rcyn4t3tkpyq.cloudfront.net.
+0800 2024-12-14 02:47:39 INFO [3579896787 38ms] dns: exchanged s.voce.chat A d3rcyn4t3tkpyq.cloudfront.net. 60 IN A 54.230.71.45
+0800 2024-12-14 02:47:39 INFO [3579896787 38ms] dns: exchanged s.voce.chat A d3rcyn4t3tkpyq.cloudfront.net. 60 IN A 54.230.71.118
+0800 2024-12-14 02:47:39 INFO [3579896787 38ms] dns: exchanged s.voce.chat A d3rcyn4t3tkpyq.cloudfront.net. 60 IN A 54.230.71.126
+0800 2024-12-14 02:47:39 INFO [3579896787 38ms] dns: exchanged s.voce.chat A d3rcyn4t3tkpyq.cloudfront.net. 60 IN A 54.230.71.17
+0800 2024-12-14 02:47:39 INFO [1559130735 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:40 ERROR [1559130735 301ms] router: timeout
+0800 2024-12-14 02:47:43 INFO [3373120338 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:43 ERROR [3373120338 300ms] router: timeout
+0800 2024-12-14 02:47:46 INFO [3035261225 0ms] inbound/vless[vless-in]: inbound multiplex connection to 1.1.1.1:53
+0800 2024-12-14 02:47:46 INFO [3035261225 5ms] dns: exchanged connectivitycheck.gstatic.com A connectivitycheck.gstatic.com. 93 IN A 142.250.76.227
+0800 2024-12-14 02:47:46 INFO [2589716888 0ms] inbound/vless[vless-in]: inbound connection from 127.0.0.1:40030
+0800 2024-12-14 02:47:46 INFO [2589716888 46ms] inbound/vless[vless-in]: [swysgh] inbound connection to sp.mux.sing-box.arpa:444
+0800 2024-12-14 02:47:46 INFO [2828090292 1ms] inbound/vless[vless-in]: inbound multiplex connection to 142.250.76.227:443
+0800 2024-12-14 02:47:46 INFO [2828090292 2ms] outbound/direct: outbound connection to 142.250.76.227:443
+0800 2024-12-14 02:47:46 INFO [3967236324 2ms] inbound/vless[vless-in]: inbound multiplex connection to 142.250.76.227:443
+0800 2024-12-14 02:47:46 INFO [3967236324 2ms] outbound/direct: outbound connection to 142.250.76.227:443
+0800 2024-12-14 02:47:48 INFO [2396041385 0ms] inbound/vless[vless-in]: inbound connection from 127.0.0.1:40042
+0800 2024-12-14 02:47:49 INFO [2396041385 202ms] inbound/vless[vless-in]: [swysgh] inbound connection to sp.mux.sing-box.arpa:444
+0800 2024-12-14 02:47:49 INFO [4207202284 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:49 ERROR [4207202284 301ms] router: timeout
+0800 2024-12-14 02:47:50 ERROR [4182996683 0ms] inbound/vless[vless-in]: process multiplex stream: read multiplex stream request: EOF
+0800 2024-12-14 02:47:50 ERROR [1083859610 0ms] inbound/vless[vless-in]: process multiplex stream: read multiplex stream request: EOF
+0800 2024-12-14 02:47:50 ERROR [3831663726 68ms] inbound/vless[vless-in]: process multiplex stream: read multiplex stream request: EOF
+0800 2024-12-14 02:47:50 ERROR [2844931498 0ms] inbound/vless[vless-in]: process multiplex stream: read multiplex stream request: EOF
+0800 2024-12-14 02:47:51 INFO [1003483624 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:51 ERROR [1003483624 301ms] router: timeout
+0800 2024-12-14 02:47:54 INFO [1576609798 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:54 ERROR [1576609798 300ms] router: timeout
+0800 2024-12-14 02:47:58 INFO [1475496981 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:58 ERROR [1475496981 301ms] router: timeout
+0800 2024-12-14 02:47:59 INFO [2537613979 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:47:59 ERROR [2537613979 301ms] router: timeout
+0800 2024-12-14 02:48:00 INFO [231372371 0ms] inbound/vless[vless-in]: inbound multiplex connection to 1.1.1.1:53
+0800 2024-12-14 02:48:00 INFO [231372371 6ms] dns: exchanged safebrowsing.googleapis.com A safebrowsing.googleapis.com. 79 IN A 142.250.197.10
+0800 2024-12-14 02:48:00 INFO [2872590539 1ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:48:00 INFO [2872590539 2ms] outbound/direct: outbound packet connection
+0800 2024-12-14 02:48:00 ERROR [2872590539 2ms] connection: listen outbound packet connection: name error
+0800 2024-12-14 02:48:02 ERROR [1742363332 1m13s] inbound/vless[vless-in]: process multiplex connection from 127.0.0.1:38324: EOF
+0800 2024-12-14 02:48:02 INFO [1381129245 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:48:02 ERROR [1381129245 301ms] router: timeout
+0800 2024-12-14 02:48:02 INFO [2948532681 0ms] inbound/vless[vless-in]: inbound connection from 127.0.0.1:47386
+0800 2024-12-14 02:48:03 INFO [2948532681 200ms] inbound/vless[vless-in]: [swysgh] inbound connection to sp.mux.sing-box.arpa:444
+0800 2024-12-14 02:48:03 INFO [3634054077 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:48:03 ERROR [3634054077 301ms] router: timeout
+0800 2024-12-14 02:48:04 INFO [1144190273 2ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:48:04 INFO [1356258187 1ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:48:04 ERROR [1779795426 2m21s] inbound/vless[vless-in]: process multiplex connection from 127.0.0.1:43808: EOF
+0800 2024-12-14 02:48:04 INFO [1144190273 300ms] outbound/direct: outbound packet connection
+0800 2024-12-14 02:48:04 ERROR [1144190273 301ms] connection: listen outbound packet connection: name error
+0800 2024-12-14 02:48:04 ERROR [1356258187 302ms] router: timeout
+0800 2024-12-14 02:48:05 INFO [3078438192 0ms] inbound/vless[vless-in]: inbound connection from 127.0.0.1:50886
+0800 2024-12-14 02:48:05 INFO [3078438192 199ms] inbound/vless[vless-in]: [swysgh] inbound connection to sp.mux.sing-box.arpa:444
+0800 2024-12-14 02:48:05 INFO [3941220856 1ms] inbound/vless[vless-in]: inbound multiplex connection to 142.250.197.10:443
+0800 2024-12-14 02:48:05 INFO [3941220856 2ms] outbound/direct: outbound connection to 142.250.197.10:443
+0800 2024-12-14 02:48:05 INFO [2214360619 2ms] inbound/vless[vless-in]: inbound multiplex connection to 203.231.242.89:52342
+0800 2024-12-14 02:48:05 INFO [2214360619 2ms] outbound/direct: outbound connection to 203.231.242.89:52342
+0800 2024-12-14 02:48:05 INFO [941652577 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:48:05 INFO [3691924956 0ms] inbound/vless[vless-in]: inbound connection from 127.0.0.1:50892
+0800 2024-12-14 02:48:05 INFO [3691924956 49ms] inbound/vless[vless-in]: [swysgh] inbound connection to sp.mux.sing-box.arpa:444
+0800 2024-12-14 02:48:05 INFO [856943718 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:48:05 ERROR [941652577 302ms] router: timeout
+0800 2024-12-14 02:48:06 ERROR [856943718 301ms] router: timeout
+0800 2024-12-14 02:48:06 INFO [2193616741 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:48:07 ERROR [2193616741 302ms] router: timeout
+0800 2024-12-14 02:48:08 INFO [1015049888 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:48:08 INFO [2266790482 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:48:08 ERROR [1015049888 301ms] router: timeout
+0800 2024-12-14 02:48:09 ERROR [2266790482 301ms] router: timeout
+0800 2024-12-14 02:48:10 INFO [2859499524 0ms] inbound/vless[vless-in]: inbound multiplex connection to 142.250.197.174:443
+0800 2024-12-14 02:48:10 INFO [2859499524 1ms] outbound/direct: outbound connection to 142.250.197.174:443
+0800 2024-12-14 02:48:10 INFO [56841885 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:48:10 ERROR [56841885 300ms] router: timeout
+0800 2024-12-14 02:48:12 ERROR [2054509275 0ms] inbound/vless[vless-in]: process multiplex stream: read multiplex stream request: EOF
+0800 2024-12-14 02:48:12 INFO [1589188188 0ms] inbound/vless[vless-in]: inbound multiplex packet connection
+0800 2024-12-14 02:48:12 ERROR [1589188188 300ms] router: timeout
+0800 2024-12-14 02:48:14 INFO [3310145264 1ms] inbound/vless[vless-in]: inbound multiplex connection to 142.250.197.174:443
+0800 2024-12-14 02:48:14 INFO [3310145264 2ms] outbound/direct: outbound connection to 142.250.197.174:443

支持我们

完整性要求

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

This comment was marked as off-topic.

Sign in to view
@swysgh

This comment was marked as off-topic.

Sign in to view
@nekohasekai nekohasekai added the bug Something isn't working label Dec 15, 2024
@vxtls
Copy link

vxtls commented Jan 17, 2025

这个BUG啥时候修，影响有点大

@swysgh

This comment has been minimized.

Sign in to view
@vxtls
Copy link

vxtls commented Jan 18, 2025

Image
这是用reality节点的情况，几乎不会出现dns解析错误,用的tproxy透明代理

@nekohasekai
Copy link
Member

如果仍然存在问题，请重新打开单独的 issues。

@swysgh
Copy link
Author

swysgh commented Jan 19, 2025

如果仍然存在问题，请重新打开单独的 issues。

好，我会重新测试并打开单独的ussue

@swysgh
Copy link
Author

swysgh commented Jan 19, 2025 •
edited
Loading

如果仍然存在问题，请重新打开单独的 issues。

测试完了，发现自己的服务端忘更新了，抱歉，一直怀疑是客户端的问题，忘了看服务端了。目前测试暂时正常，客户端正式版打开uot依然不行，测试版还没试uot，等之后有空再进行测试。另外还有很奇怪的地方，beta8的服务端能接收一条udp,然后貌似就关闭连接了，查看日志发现每次进行连接都会开启新的udp连接，nc貌似有识别，只能通过第一次连接的ip和端口进行连接，可能这就是造成这个现象的原因。dns正常，这是我当时总结的现象：

ss的udp不同，使用了nc进行测试，发现可能和服务端也有关系。使用正式版的服务端和客户端时，nc能正常发送，使用测试版服务端时，nc只能发送一条，之后的就收不到了，具体截图也不方便，可以测试一下。当双端都是测试版时，nc隔了好久才收到第一条消息，后面有勉强能收到几条，开启uot后直接一条都收不到。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mazzz1y @nekohasekai @swysgh @vxtls