Open 2dust opened 8 months ago
我这里windows 10 无论何版本都不能开启TUN模式上网,不是断网就是DNS无法解析或者虚拟网卡无法开启。我还试了nekoray开启TUN模式也不能上网。TUN模式还不成熟。还有v2rayN 6.31版本对Hysteria2类型的节点无法测速。
@2dust how can I downgrade to 6.23 without losing configs and groups? is there a proper way for that or should I add them again?
@2dust how can I downgrade to 6.23 without losing configs and groups? is there a proper way for that or should I add them again?
Copy the guiConfigs folder in the 6.31 ,paste to 6.23 , replace
我的情况是:
其他说明:以上情况均是在 dns 设置中的 singbox dns设置导入的默认配置的情况下产生的,xray的dns没问题(我暂时也还在研究singbox官网的配置文档,就导入用默认的了)
https://github.com/chika0801/sing-box-examples/blob/main/Tun/config_client_windows_local_dns.json @Yuq-q 按照这个模板填入,你用自定义配置跑下结果
我这里windows 10 无论何版本都不能开启TUN模式上网,不是断网就是DNS无法解析或者虚拟网卡无法开启。我还试了nekoray开启TUN模式也不能上网。TUN模式还不成熟。还有v2rayN 6.31版本对Hysteria2类型的节点无法测速。
Hysteria2测速会解决的,需要时间
https://github.com/chika0801/sing-box-examples/blob/main/Tun/config_client_windows_local_dns.json @Yuq-q 按照这个模板填入,你用自定义配置跑下结果
这个用这个模版的DNS配置转换的config.json会有错
[31mFATAL[0m[0000] create service: parse route options: parse dns rule[1]: missing conditions
Cannot mix synchronous and asynchronous operation on process stream.
另外 就像我上面提到的 其实如果用默认的DNS的话 我这儿的tun是可以使用的(虽然DNS会有问题,但是我看了默认的dns配置,好像又没啥问题),只是不论直连还是代理都会被统计到proxy的网速和流量统计中 。(如果是自己用命令行手动运行singbox的话,还真分辨不出到底配置好没,因为至少能将就用 ) 至于上面提到的情况2还是存在 .
考不考虑加个导入外部config.json配置的选项?有时候图方便在外部改了DNS或者是一些没有经V2rayN里图形化 的配置 等打开v2rayN后又变成之前的了
singbox 1.8 版本還要去除geoip,要不等singbox 1.8穩定了再改tun的config?
如果6.31版本配1.7.6的singbox使用 tun確實會有DNS解析的問題,能用但是有報錯。這個是那邊沒有出現的issue。
+0800 2023-12-24 22:37:46 ERROR [953232222 736ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:37:47 ERROR [3160916494 1.4s] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:37:47 ERROR [1043110566 1.76s] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:37:47 ERROR [1597419060 994ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:37:48 ERROR [3890520578 1.73s] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:37:48 ERROR [3657397793 2.71s] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:37:48 ERROR [1842071952 580ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:37:48 ERROR [25680338 587ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:37:50 ERROR [1801902349 3.48s] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:37:53 ERROR [524543594 1.59s] inbound/tun[tun-in]: download: ws closed: 1000
+0800 2023-12-24 22:37:56 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context deadline exceeded
+0800 2023-12-24 22:37:56 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context canceled
+0800 2023-12-24 22:38:02 ERROR dns: exchange failed for 5.5.5.223.in-addr.arpa. IN PTR: context deadline exceeded
+0800 2023-12-24 22:38:03 ERROR dns: exchange failed for 5.5.5.223.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:03 ERROR dns: exchange failed for 5.5.5.223.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:03 ERROR dns: exchange failed for 5.5.5.223.in-addr.arpa. IN PTR: use of closed network connection
+0800 2023-12-24 22:38:03 ERROR dns: exchange failed for 5.5.5.223.in-addr.arpa. IN PTR: use of closed network connection
+0800 2023-12-24 22:38:03 ERROR dns: exchange failed for 5.5.5.223.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:03 ERROR dns: exchange failed for 5.5.5.223.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:14 ERROR dns: exchange failed for dns.msftncsi.com. IN PTR: context deadline exceeded
+0800 2023-12-24 22:38:14 ERROR dns: exchange failed for dns.msftncsi.com. IN PTR: context canceled
+0800 2023-12-24 22:38:14 ERROR dns: exchange failed for dns.msftncsi.com. IN PTR: context canceled
+0800 2023-12-24 22:38:15 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context deadline exceeded
+0800 2023-12-24 22:38:15 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context canceled
+0800 2023-12-24 22:38:15 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context canceled
+0800 2023-12-24 22:38:15 ERROR dns: exchange failed for dns.msftncsi.com. IN PTR: context deadline exceeded
+0800 2023-12-24 22:38:15 ERROR dns: exchange failed for dns.msftncsi.com. IN PTR: context canceled
+0800 2023-12-24 22:38:15 ERROR dns: exchange failed for 3.0.19.172.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:15 ERROR dns: exchange failed for dns.msftncsi.com. IN PTR: context canceled
+0800 2023-12-24 22:38:15 ERROR dns: exchange failed for dns.msftncsi.com. IN PTR: context canceled
+0800 2023-12-24 22:38:21 ERROR [1193530906 739ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:38:21 ERROR [4134853019 739ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:38:25 ERROR dns: exchange failed for 3.0.19.172.in-addr.arpa. IN PTR: context deadline exceeded
+0800 2023-12-24 22:38:25 ERROR [3961329150 1.59s] inbound/tun[tun-in]: download: ws closed: 1000
+0800 2023-12-24 22:38:25 ERROR dns: exchange failed for 3.0.19.172.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:26 ERROR dns: exchange failed for 3.0.19.172.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:26 ERROR dns: exchange failed for 3.0.19.172.in-addr.arpa. IN PTR: context deadline exceeded
+0800 2023-12-24 22:38:27 ERROR dns: exchange failed for 3.0.19.172.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:27 ERROR dns: exchange failed for 3.0.19.172.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:30 ERROR [3494475206 583ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:38:30 ERROR [60775563 576ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:38:30 ERROR [3601952082 591ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:38:33 ERROR [4211754508 567ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:38:33 ERROR [417084348 579ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:38:33 ERROR [3957176018 585ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:38:33 ERROR [1740102031 575ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:38:33 ERROR [3465481151 576ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:38:33 ERROR [3421976560 576ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:38:33 ERROR [188839947 580ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:38:34 ERROR [3367077630 1.57s] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:38:37 ERROR dns: exchange failed for 2.0.19.172.in-addr.arpa. IN PTR: context deadline exceeded
+0800 2023-12-24 22:38:37 ERROR dns: exchange failed for 2.0.19.172.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:37 ERROR dns: exchange failed for 2.0.19.172.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:37 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context deadline exceeded
+0800 2023-12-24 22:38:37 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context canceled
+0800 2023-12-24 22:38:37 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context canceled
+0800 2023-12-24 22:38:38 ERROR dns: exchange failed for 2.0.19.172.in-addr.arpa. IN PTR: context deadline exceeded
+0800 2023-12-24 22:38:38 ERROR dns: exchange failed for 2.0.19.172.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:38 ERROR dns: exchange failed for 68.221.251.142.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:38 ERROR dns: exchange failed for 2.0.19.172.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:38 ERROR dns: exchange failed for 2.0.19.172.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:47 ERROR dns: exchange failed for 68.221.251.142.in-addr.arpa. IN PTR: context deadline exceeded
+0800 2023-12-24 22:38:47 ERROR dns: exchange failed for 68.221.251.142.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:47 ERROR dns: exchange failed for 68.221.251.142.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:47 ERROR dns: exchange failed for 68.221.251.142.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:50 ERROR dns: exchange failed for 68.221.251.142.in-addr.arpa. IN PTR: context deadline exceeded
+0800 2023-12-24 22:38:50 ERROR dns: exchange failed for 68.221.251.142.in-addr.arpa. IN PTR: context canceled
+0800 2023-12-24 22:38:56 ERROR [1498328190 727ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:38:56 ERROR [2143417818 728ms] inbound/tun[tun-in]: download: tls: protocol is shutdown
+0800 2023-12-24 22:38:57 ERROR [3786743278 1m11s] inbound/tun[tun-in]: download: ws closed: 1000
singbox 1.8 版本還要去除geoip,要不等singbox 1.8穩定了再改tun的config?
如果6.31版本配1.7.6的singbox使用 tun確實會有DNS解析的問題,能用但是有報錯。這個是那邊沒有出現的issue。
+0800 2023-12-24 22:37:46 ERROR [953232222 736ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:37:47 ERROR [3160916494 1.4s] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:37:47 ERROR [1043110566 1.76s] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:37:47 ERROR [1597419060 994ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:37:48 ERROR [3890520578 1.73s] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:37:48 ERROR [3657397793 2.71s] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:37:48 ERROR [1842071952 580ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:37:48 ERROR [25680338 587ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:37:50 ERROR [1801902349 3.48s] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:37:53 ERROR [524543594 1.59s] inbound/tun[tun-in]: download: ws closed: 1000 +0800 2023-12-24 22:37:56 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context deadline exceeded +0800 2023-12-24 22:37:56 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context canceled +0800 2023-12-24 22:38:02 ERROR dns: exchange failed for 5.5.5.223.in-addr.arpa. IN PTR: context deadline exceeded +0800 2023-12-24 22:38:03 ERROR dns: exchange failed for 5.5.5.223.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:03 ERROR dns: exchange failed for 5.5.5.223.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:03 ERROR dns: exchange failed for 5.5.5.223.in-addr.arpa. IN PTR: use of closed network connection +0800 2023-12-24 22:38:03 ERROR dns: exchange failed for 5.5.5.223.in-addr.arpa. IN PTR: use of closed network connection +0800 2023-12-24 22:38:03 ERROR dns: exchange failed for 5.5.5.223.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:03 ERROR dns: exchange failed for 5.5.5.223.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:14 ERROR dns: exchange failed for dns.msftncsi.com. IN PTR: context deadline exceeded +0800 2023-12-24 22:38:14 ERROR dns: exchange failed for dns.msftncsi.com. IN PTR: context canceled +0800 2023-12-24 22:38:14 ERROR dns: exchange failed for dns.msftncsi.com. IN PTR: context canceled +0800 2023-12-24 22:38:15 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context deadline exceeded +0800 2023-12-24 22:38:15 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context canceled +0800 2023-12-24 22:38:15 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context canceled +0800 2023-12-24 22:38:15 ERROR dns: exchange failed for dns.msftncsi.com. IN PTR: context deadline exceeded +0800 2023-12-24 22:38:15 ERROR dns: exchange failed for dns.msftncsi.com. IN PTR: context canceled +0800 2023-12-24 22:38:15 ERROR dns: exchange failed for 3.0.19.172.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:15 ERROR dns: exchange failed for dns.msftncsi.com. IN PTR: context canceled +0800 2023-12-24 22:38:15 ERROR dns: exchange failed for dns.msftncsi.com. IN PTR: context canceled +0800 2023-12-24 22:38:21 ERROR [1193530906 739ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:38:21 ERROR [4134853019 739ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:38:25 ERROR dns: exchange failed for 3.0.19.172.in-addr.arpa. IN PTR: context deadline exceeded +0800 2023-12-24 22:38:25 ERROR [3961329150 1.59s] inbound/tun[tun-in]: download: ws closed: 1000 +0800 2023-12-24 22:38:25 ERROR dns: exchange failed for 3.0.19.172.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:26 ERROR dns: exchange failed for 3.0.19.172.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:26 ERROR dns: exchange failed for 3.0.19.172.in-addr.arpa. IN PTR: context deadline exceeded +0800 2023-12-24 22:38:27 ERROR dns: exchange failed for 3.0.19.172.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:27 ERROR dns: exchange failed for 3.0.19.172.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:30 ERROR [3494475206 583ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:38:30 ERROR [60775563 576ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:38:30 ERROR [3601952082 591ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:38:33 ERROR [4211754508 567ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:38:33 ERROR [417084348 579ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:38:33 ERROR [3957176018 585ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:38:33 ERROR [1740102031 575ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:38:33 ERROR [3465481151 576ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:38:33 ERROR [3421976560 576ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:38:33 ERROR [188839947 580ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:38:34 ERROR [3367077630 1.57s] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:38:37 ERROR dns: exchange failed for 2.0.19.172.in-addr.arpa. IN PTR: context deadline exceeded +0800 2023-12-24 22:38:37 ERROR dns: exchange failed for 2.0.19.172.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:37 ERROR dns: exchange failed for 2.0.19.172.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:37 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context deadline exceeded +0800 2023-12-24 22:38:37 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context canceled +0800 2023-12-24 22:38:37 ERROR dns: exchange failed for CKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. IN SRV: context canceled +0800 2023-12-24 22:38:38 ERROR dns: exchange failed for 2.0.19.172.in-addr.arpa. IN PTR: context deadline exceeded +0800 2023-12-24 22:38:38 ERROR dns: exchange failed for 2.0.19.172.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:38 ERROR dns: exchange failed for 68.221.251.142.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:38 ERROR dns: exchange failed for 2.0.19.172.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:38 ERROR dns: exchange failed for 2.0.19.172.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:47 ERROR dns: exchange failed for 68.221.251.142.in-addr.arpa. IN PTR: context deadline exceeded +0800 2023-12-24 22:38:47 ERROR dns: exchange failed for 68.221.251.142.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:47 ERROR dns: exchange failed for 68.221.251.142.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:47 ERROR dns: exchange failed for 68.221.251.142.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:50 ERROR dns: exchange failed for 68.221.251.142.in-addr.arpa. IN PTR: context deadline exceeded +0800 2023-12-24 22:38:50 ERROR dns: exchange failed for 68.221.251.142.in-addr.arpa. IN PTR: context canceled +0800 2023-12-24 22:38:56 ERROR [1498328190 727ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:38:56 ERROR [2143417818 728ms] inbound/tun[tun-in]: download: tls: protocol is shutdown +0800 2023-12-24 22:38:57 ERROR [3786743278 1m11s] inbound/tun[tun-in]: download: ws closed: 1000
把完整配置发出来
更新之后打开tun就无法监听socks,后来是改了guiNConfig.json下的 "enableExInbound": true,就可以同时用了,但是日志一直在告警:wsasend: An established connection was aborted by the software in your host machine. wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
正确,
把完整配置发出来
我使用的就是默认的config
如果仅仅使用sing box作为内核而不启动tun的话,是没有这些DNS error的。
不是tunconfig.json,6.31在开启tun后路由规则会从v2ray格式自动转换成sing-box格式,应该是开启tun后的config.json,tunconfig.json是6.23的
tunConfig.json 在6.31已经废弃了 需要查看的是config.json @NSIOISN
tunConfig.json 在6.31已经废弃了 需要查看的是config.json @NSIOISN
抱歉,这份是我开启tun后的配置,仅去除了server name config.json
作为对比,这是仅用sing box内核不开启tun的配置 config.json
tunConfig.json 在6.31已经废弃了 需要查看的是config.json @NSIOISN
抱歉,这份是我开启tun后的配置,仅去除了server name config.json
作为对比,这是仅用sing box内核不开启tun的配置 config.json
从config上看并没有什么问题 等是否有人能看出问题吧
tunConfig.json 在6.31已经废弃了 需要查看的是config.json @NSIOISN
抱歉,这份是我开启tun后的配置,仅去除了server name config.json 作为对比,这是仅用sing box内核不开启tun的配置 config.json
从config上看并没有什么问题 等是否有人能看出问题吧
The TUN problem which doesn't show up in Network Connections has been fixed in the new version of v2rayN 6.32 https://github.com/2dust/v2rayN/releases/tag/6.32
https://github.com/2dust/v2rayN/issues/4012 has been resolved. Thank you @2dust
Hey guys. I have an issue with new version. After updating to 6.31, when I enable "Enable Tun" button, it gives me this error and not working. Before updating it was working very well! Any idea?
Seems like there is something wrong with DNS address.
Hey guys. I have an issue with new version. After updating to 6.31, when I enable "Enable Tun" button, it gives me this error and not working. Before updating it was working very well! Any idea?
Seems like there is something wrong with DNS address.
you should update your V2rayN app to 6.32. the link: https://github.com/2dust/v2rayN/releases/tag/6.32 something fixed in new version.
Hey guys. I have an issue with new version. After updating to 6.31, when I enable "Enable Tun" button, it gives me this error and not working. Before updating it was working very well! Any idea? Seems like there is something wrong with DNS address.
you should update your V2rayN app to 6.32. the link: https://github.com/2dust/v2rayN/releases/tag/6.32 something fixed in new version.
It works now! Thanks!
我更新到6.32还是一样的问题,感觉没变啊
我更新到6.32还是一样的问题,感觉没变啊
在tun设置中打开strict route试试
I updated to 6.32 and still have the same problem. I feel the same.
Try turning off ipv6 in Tun settings and check
我更新到6.32还是一样的问题,感觉没变啊
在tun设置中打开strict route试试
默认开着的,不是这个问题
I updated to 6.32 and still have the same problem. I feel the same.
Try turning off ipv6 in Tun settings and check
It works now, and I hope it is the reason.
2024/01/18 09:12:59 System proxy setting is changedForcedClear
2024/01/18 09:13:02 The ping of current service: 921 ms
-0800 2024-01-18 09:15:36 ERROR [3972850357 2m4s] inbound/tun[tun-in]: download: read tcp 192.168.31.171:9903->74.48.186.57:40916: wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
{
"servers": [
{
"tag": "remote",
"address": "https://1.1.1.1/dns-query",
"detour": "proxy"
},
{
"tag": "local",
"address": "223.5.5.5",
"detour": "direct"
},
{
"tag": "block",
"address": "rcode://success"
}
],
"rules": [
{
"geosite": [
"cn"
],
"server": "local",
"disable_cache": true
},
{
"geosite": [
"category-ads-all"
],
"server": "block",
"disable_cache": true
}
],
"strategy": "ipv4_only"
}
@2dust 问题已修复,修改配置由 "address": "tcp://8.8.8.8", -> 修改为 "address": "udp://8.8.8.8",即可(反正vmess是可以用的)
@2dust 问题已修复,修改配置由 "address": "tcp://8.8.8.8", -> 修改为 "address": "udp://8.8.8.8",即可(反正vmess是可以用的)
谢谢反馈,您这个服务器特殊吧,一般都支持默认的DNS
@2dust 问题已修复,修改配置由 "address": "tcp://8.8.8.8", -> 修改为 "address": "udp://8.8.8.8",即可(反正vmess是可以用的)
谢谢反馈,您这个服务器特殊吧,一般都支持默认的DNS
关于TUN模式启动失败,网卡不断重启的问题,可能是由于缺少TUN驱动,可以通过https://download.wireguard.com/windows-client/wireguard-amd64-0.5.3.msi下载wireguard提供的tun驱动解决这个问题
版本:v6.35
系统:win10专业版
类型:vmess
线路在不开启Tun模式的情况下正常,一旦开启Tun就断网了,尝试过其他issue里说的不断重启Tun也没用。
日志:Microsoft Windows NT 10.0.19045.0 - 64 启动服务(2024/02/18 17:18:20)... 2024/02/18 17:18:21 系统代理设置改变ForcedChange +0800 2024-02-18 17:18:30 WARN inbound/tun[tun-in]: open tun interface take too much time to finish! 2024/02/18 17:18:33 当前服务的真连接延迟: -1 ms FATAL[0015] start service: initialize inbound/tun[tun-in]: configure tun interface: Cannot create a file when that file already exists. Microsoft Windows NT 10.0.19045.0 - 64 启动服务(2024/02/18 17:18:36)... Tun mode restart the core once panic: unaligned 64-bit atomic operation
版本:v6.35 系统:win10专业版 类型:vmess 线路在不开启Tun模式的情况下正常,一旦开启Tun就断网了,尝试过其他issue里说的不断重启Tun也没用。
日志:Microsoft Windows NT 10.0.19045.0 - 64 启动服务(2024/02/18 17:18:20)... 2024/02/18 17:18:21 系统代理设置改变ForcedChange +0800 2024-02-18 17:18:30 WARN inbound/tun[tun-in]: open tun interface take too much time to finish! 2024/02/18 17:18:33 当前服务的真连接延迟: -1 ms FATAL[0015] start service: initialize inbound/tun[tun-in]: configure tun interface: Cannot create a file when that file already exists. Microsoft Windows NT 10.0.19045.0 - 64 启动服务(2024/02/18 17:18:36)... Tun mode restart the core once panic: unaligned 64-bit atomic operation
我建议下载驱动后再运行一下试试,你的TUN网卡没有成功启动 https://download.wireguard.com/windows-client/wireguard-amd64-0.5.3.msi
by default, windows (up to 11, brand new install tested) preconfigured the LLMNR policy: Turn Off Multicast Name Resolution with not configured, when enabled it (for team kitten or aka. clash team), in this circumstances which will cause poor performance for sing-box deal with DNS and it slowdown the entire network, also for NekoBox since they share the same core. btw you guys are awesome 👍
借楼问一下:要实现智能代理(包括whatsapp等UWP应用),在开启TUN模式后,“系统代理”和“路由”这2个选项应该如何选择?
tun开启时会关闭系统代理,路由是生效的
tun开启时会关闭系统代理,路由是生效的
意思是选择系统代理选项下的清除系统代理、自动配置系统代理、不改变系统代理、PAC模式中的任一项都不会生效吗?而路由下的绕过大陆、黑名单和全局是可以生效,在开启tun的情况下,路由选择全局是所有流量都走代理吗?或者说开启tun的情况下,路由如何选是智能代理(包括whatsapp等UWP应用)?
tun开启时会关闭系统代理,路由是生效的
意思是选择系统代理选项下的清除系统代理、自动配置系统代理、不改变系统代理、PAC模式中的任一项都不会生效吗?而路由下的绕过大陆、黑名单和全局是可以生效,在开启tun的情况下,路由选择全局是所有流量都走代理吗?或者说开启tun的情况下,路由如何选是智能代理(包括whatsapp等UWP应用)?
你可以看看guiConfigs/config.json文件 开tun会自动关闭系统代理,路由是core行为,所以你选择了上面就是什么。如果要代理exe,可以在路由设置中加入进程名
我的情况是:
- 管理员启动 v2rayN , 打开Tun ,确保虚拟网卡正确加载,可以正常使用tun,但是不论是在消耗 direct 流量还是 proxy 流量 ,当前的网速都会被统计到 v2rayN 右下角的 proxy 的网速中,比如打开https://test.ustc.edu.cn/ ,在流量消耗的过程中,此网页显示的 ip 是未代理的运营商 ip ,但是 v2rayN 右下角的网速中 是proxy在跳动
- 管理员启动 v2rayN , 打开Tun ,确保虚拟网卡正确加载,此时打开电脑热点,电脑访问任意网页,打开任务管理器会发现 v2rayN CPU占用暴增,一会就卡死了,情况1虽然 direct 的网速不能正确显示在 direct 中,但是至少能将就用,但是开启了热点后就用不了,会不会是 [Bug]: V6.25 中,启动 tun 模式后,config.json 中缺少 http 和 socks 端口监听的配置 #3915 (comment) 中 enableExInbound 对应函数的问题?(不过不管是true还是false都会卡死,可能也不是这儿的问题,这里只是怀疑)
其他说明:以上情况均是在 dns 设置中的 singbox dns设置导入的默认配置的情况下产生的,xray的dns没问题(我暂时也还在研究singbox官网的配置文档,就导入用默认的了)
3.39版本,和你是同样的问题,开启Tun后软件右下角流量监控现实全部走的Proxy,你发现问题了吗?
Why do you even need to use Sing-Box completely instead of combining them both like NekoRay? Sing-Box does not support mux.cool/fragment/xray's quic and mkcp and more, you can't convert xray's conf to sing-box and Xray-core does not support sing-box's mux (connection will fail) This was a bad idea to convert xray/v2ray configs to sing-box for Tun!
我的情况是:
- 管理员启动 v2rayN , 打开Tun ,确保虚拟网卡正确加载,可以正常使用tun,但是不论是在消耗 direct 流量还是 proxy 流量 ,当前的网速都会被统计到 v2rayN 右下角的 proxy 的网速中,比如打开https://test.ustc.edu.cn/ ,在流量消耗的过程中,此网页显示的 ip 是未代理的运营商 ip ,但是 v2rayN 右下角的网速中 是proxy在跳动
- 管理员启动 v2rayN , 打开Tun ,确保虚拟网卡正确加载,此时打开电脑热点,电脑访问任意网页,打开任务管理器会发现 v2rayN CPU占用暴增,一会就卡死了,情况1虽然 direct 的网速不能正确显示在 direct 中,但是至少能将就用,但是开启了热点后就用不了,会不会是 [Bug]: V6.25 中,启动 tun 模式后,config.json 中缺少 http 和 socks 端口监听的配置 #3915 (comment) 中 enableExInbound 对应函数的问题?(不过不管是true还是false都会卡死,可能也不是这儿的问题,这里只是怀疑)
其他说明:以上情况均是在 dns 设置中的 singbox dns设置导入的默认配置的情况下产生的,xray的dns没问题(我暂时也还在研究singbox官网的配置文档,就导入用默认的了)
3.39版本,和你是同样的问题,开启Tun后软件右下角流量监控现实全部走的Proxy,你发现问题了吗?
目前还是有这个问题,不过实际上是分流了的,https://ipw.cn/ip/ 你可以看到这个 查ip的国内网站 显示的ip归属地就是你国内运营商的, 你换个 https://www.ipaddress.com/ 国外的查ip的网站 显示的就是代理的ip 实际上是分流了, 不过都会显示proxy,将就用吧
tun模式后. foxmail无法收邮件问题
tunConfig.json 在6.31已经废弃了 需要查看的是config.json @NSIOISN
Well, this problem was solved for me with this method: Put alpn in the configuration of anything except h2, the problem will be solved and tun mode will be turned on
Why do you even need to use Sing-Box completely instead of combining them both like NekoRay? Sing-Box does not support mux.cool/fragment/xray's quic and mkcp and more, you can't convert xray's conf to sing-box and Xray-core does not support sing-box's mux (connection will fail) This was a bad idea to convert xray/v2ray configs to sing-box for Tun!
Well, this problem was solved for me with this method: Put alpn in the configuration of anything except h2, the problem will be solved and tun mode will be turned on
v6.33,TUN模式會有一些問題:
* 會_**過幾分鐘**_就會連不上YouTube和Google搜尋,要點擊“reload”重新加載才行。或者把Google Chrome裏面的安全DNS打開也可以解決問題,但還是會==復發==。 * 有抓到一個日誌:
2024/01/18 09:12:59 System proxy setting is changedForcedClear 2024/01/18 09:13:02 The ping of current service: 921 ms -0800 2024-01-18 09:15:36 ERROR [3972850357 2m4s] inbound/tun[tun-in]: download: read tcp 192.168.31.171:9903->74.48.186.57:40916: wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
* DNS的JSON
{ "servers": [ { "tag": "remote", "address": "https://1.1.1.1/dns-query", "detour": "proxy" }, { "tag": "local", "address": "223.5.5.5", "detour": "direct" }, { "tag": "block", "address": "rcode://success" } ], "rules": [ { "geosite": [ "cn" ], "server": "local", "disable_cache": true }, { "geosite": [ "category-ads-all" ], "server": "block", "disable_cache": true } ], "strategy": "ipv4_only" }
Well, this problem was solved for me with this method: Put alpn in the configuration of anything except h2, the problem will be solved and tun mode will be turned on
我的情况是:
1. 管理员启动 v2rayN , 打开Tun ,确保虚拟网卡正确加载,可以正常使用tun,**但是**不论是在消耗 direct 流量还是 proxy 流量 ,当前的网速都会被统计到 v2rayN 右下角的 proxy 的网速中,比如打开https://test.ustc.edu.cn/ ,在流量消耗的过程中,此网页显示的 ip 是未代理的运营商 ip ,但是 v2rayN 右下角的网速中 是proxy在跳动 2. 管理员启动 v2rayN , 打开Tun ,确保虚拟网卡正确加载,此时打开电脑热点,电脑访问任意网页,打开任务管理器会发现 v2rayN CPU占用暴增,一会就卡死了,情况1虽然 direct 的网速不能正确显示在 direct 中,但是至少能将就用,但是开启了热点后就用不了,会不会是 [[Bug]: V6.25 中,启动 tun 模式后,config.json 中缺少 http 和 socks 端口监听的配置 #3915 (comment)](https://github.com/2dust/v2rayN/issues/3915#issuecomment-1575484412) 中 enableExInbound 对应函数的问题?(不过不管是true还是false都会卡死,可能也不是这儿的问题,这里只是怀疑) ![image](https://private-user-images.githubusercontent.com/57177286/292673498-8f1b51d2-226c-4f9f-a91c-5cfc625a816d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTE1Nzc3ODQsIm5iZiI6MTcxMTU3NzQ4NCwicGF0aCI6Ii81NzE3NzI4Ni8yOTI2NzM0OTgtOGYxYjUxZDItMjI2Yy00ZjlmLWE5MWMtNWNmYzYyNWE4MTZkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAzMjclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMzI3VDIyMTEyNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQ2ZGEwNjYzMzVkMDc3YzgzNWNiZTE3OWI5MGY1MmJjYWZiM2Q3ZjUyNDk4MmE0ZTIzMjJjMDJhMzExN2RmNzUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.DIZ3sAlC8Yavn6UFjyOhO2SiO38hwwHn_0g5IY3ZVSg)
其他说明:以上情况均是在 dns 设置中的 singbox dns设置导入的默认配置的情况下产生的,xray的dns没问题(我暂时也还在研究singbox官网的配置文档,就导入用默认的了)
Well, this problem was solved for me with this method: Put alpn in the configuration of anything except h2, the problem will be solved and tun mode will be turned on
软件版本6.28,已更新最新SINGBOX内核。 相同的设置,在其他两台WIN11的电脑上可以正常开启TUN,并转发流量。但是在WIN10电脑上无法成功创建singbox虚拟网卡。提示如下:
启动服务(2024/04/07 20:41:36)... 2024/04/07 20:41:37 系统代理设置改变ForcedChange [31mFATAL[0m[0006] start service: initialize inbound/tun[tun-in]: configure tun interface: set ipv6 address: Element not found.
尝试过重置网络,重新安装网络驱动,开启路由器的IPV6等均无效。尝试使用CLASH的TUN模式,用管理员权限运行后,可以创建虚拟网卡,但是无法安装服务模式,提示无用户权限。虚拟网卡显示网络电缆被拔出。
this is v2rayn 6.42 xray1.8.10 singbox 1.8.11
问题包括两部分:
首先,我使用了xray,在开启tun模式后,关于网络连接的log消失了。
其次,偶尔会出现类似如下的errorlog:ERROR [1047510101 20.99s] inbound/tun[tun-in]: download: raw-read tcp 192.168.1.104:61132->23.210.215.73:443: An existing connection was forcibly closed by the remote host.
反映在具体情况上,就是原本可以使用chatgpt的节点在开启tun模式后,变得无法使用。但是目前为止,可以完成国内外的网站访问。一些游戏(如战争雷霆)登陆不进去
this is v2rayn 6.42 xray1.8.10 singbox 1.8.11
问题包括两部分:
首先,我使用了xray,在开启tun模式后,关于网络连接的log消失了。
其次,偶尔会出现类似如下的errorlog:ERROR [1047510101 20.99s] inbound/tun[tun-in]: download: raw-read tcp 192.168.1.104:61132->23.210.215.73:443: An existing connection was forcibly closed by the remote host.
反映在具体情况上,就是原本可以使用chatgpt的节点在开启tun模式后,变得无法使用。但是目前为止,可以完成国内外的网站访问。一些游戏(如战争雷霆)登陆不进去
上条评论发送于tun模式下,立马又蹦出来一条: +0800 2024-04-10 21:45:11 ERROR [3607721847 2m13s] inbound/tun[tun-in]: download: raw-read tcp 192.168.1.104:63212->202.89.233.101:443: An existing connection was forcibly closed by the remote host.
还没好啊,tun模式死活连不上网
Microsoft Windows NT 10.0.22631.0 - 64
Start service (2024/04/22 20:59:14)...
2024/04/22 20:59:15 System proxy setting is changedForcedChange
2024/04/22 20:59:18 The ping of current service: 364 ms
+0330 2024-04-22 20:59:24 WARN inbound/tun[tun-in]: open tun interface take too much time to finish!
FATAL[0015] start service: initialize inbound/tun[tun-in]: configure tun interface: The system cannot find the file specified.
Microsoft Windows NT 10.0.22631.0 - 64
Start service (2024/04/22 20:59:30)...
Tun mode restart the core once
+0330 2024-04-22 20:59:40 WARN inbound/tun[tun-in]: open tun interface take too much time to finish!
FATAL[0015] start service: initialize inbound/tun[tun-in]: configure tun interface: The system cannot find the file specified.
tun mode doesnt work ver 6.43 it only works in 6.23 and it uses 43% of my cpu
难受啊,上周发现突然TUN失效了,重装了中文win11系统后,还是不行,装了英文系统可以用了,然后今天TUN模式可以打开但是上不了网,现在是打开tun模式连虚拟网卡都不能用了,6.31.6.33.6.43都试过了感觉是WIN11更新的问题了
难受啊,上周发现突然TUN失效了,重装了中文win11系统后,还是不行,装了英文系统可以用了,然后今天TUN模式可以打开但是上不了网,现在是打开tun模式连虚拟网卡都不能用了,6.31.6.33.6.43都试过了感觉是WIN11更新的问题了
是window的问题?我win10也不行啊
从 v6.50 开始,Tun模式的启动内核已经有新的模式
试一试替换下面的dns设置