v2rayN icon indicating copy to clipboard operation
v2rayN copied to clipboard

Published 20 hours ago • verified publisher icon 2dust

关于6.31+版本Tun模式问题的统一回复

Open 2dust opened this issue 6 months ago • 73 comments 

- Q：为什么v6.23版本的Tun可用，而v6.31版本的有问题
- A：因为v6.23的只用sing-box开了Tun入口，出口还是用原始core处理；v6.31是全部用sing-box处理，这可能会导致部分节点无法正常运行。
- 解决办法：退回到v6.23，等待xray-core加入Tun。
- 同时您也可帮忙反馈v6.31产生的sing-box config是否正确；毕竟众人拾柴火焰高

- Q：为什么路由不正确，DNS不正确
- A：因为开发者也是初学sing-box配置，需要大家帮忙
- 解决办法：帮忙反馈v6.31产生的sing-box config是否正确

- Q：为什么没有看到sing-box的虚拟网卡
- A：v2rayN只是个GUI，此问题是core没有正常运行或系统问题
- 解决办法：这个请先查看是否有运行错误日志；日志正常则大概率是系统问题，可到sing-box 项目查看是否有类似反馈

已知问题，热点和tun模式冲突，如果要开热点请不要使用tun模式

试一试替换下面的dns设置

{
  "servers": [
    {
      "tag": "remote",
      "address": "tcp://8.8.8.8",
      "strategy": "ipv4_only",
      "detour": "proxy"
    },
    {
      "tag": "local",
      "address": "223.5.5.5",
      "strategy": "ipv4_only",
      "detour": "direct"
    },
    {
      "tag": "block",
      "address": "rcode://success"
    }
  ],
  "rules": [
    {
      "geosite": [
        "geolocation-!cn"
      ],
      "server": "remote"
    },
    {
      "geosite": [
        "category-ads-all"
      ],
      "server": "block"
    }
  ]
}


{
    "servers": [
        {
            "tag": "local",
            "address": "https://dns.alidns.com/dns-query",
            "address_resolver": "dns-resolver",
            "detour": "direct"
        },
        {
            "tag": "remote",
            "address": "https://cloudflare-dns.com/dns-query",
            "address_resolver": "dns-resolver",
            "detour": "proxy"
        },
        {
            "tag": "block",
            "address": "rcode://success"
        },
        {
            "tag": "dns-resolver",
            "address": "223.5.5.5",
            "detour": "direct"
        }
    ],
    "rules": [
        {
            "geosite": [
                "geolocation-!cn"
            ],
            "server": "remote"
        },
        {
            "outbound": "any",
            "server": "local"
        }
    ],
    "final": "remote",
    "strategy": "prefer_ipv4"
}

2dust avatar Dec 24 '23 09:12 2dust

我这里windows 10 无论何版本都不能开启TUN模式上网，不是断网就是DNS无法解析或者虚拟网卡无法开启。我还试了nekoray开启TUN模式也不能上网。TUN模式还不成熟。还有v2rayN 6.31版本对Hysteria2类型的节点无法测速。

good-bay avatar Dec 24 '23 10:12 good-bay

@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?

X-Oracle avatar Dec 24 '23 11:12 X-Oracle

@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

Kukuair avatar Dec 24 '23 13:12 Kukuair

我的情况是：

  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 中，但是至少能将就用，但是开启了热点后就用不了，会不会是 https://github.com/2dust/v2rayN/issues/3915#issuecomment-1575484412 中 enableExInbound 对应函数的问题？（不过不管是true还是false都会卡死，可能也不是这儿的问题，这里只是怀疑） image

其他说明：以上情况均是在 dns 设置中的 singbox dns设置导入的默认配置的情况下产生的，xray的dns没问题（我暂时也还在研究singbox官网的配置文档，就导入用默认的了）

Kukuair avatar Dec 24 '23 14:12 Kukuair

https://github.com/chika0801/sing-box-examples/blob/main/Tun/config_client_windows_local_dns.json @Yuq-q 按照这个模板填入，你用自定义配置跑下结果

2dust avatar Dec 25 '23 08:12 2dust

我这里windows 10 无论何版本都不能开启TUN模式上网，不是断网就是DNS无法解析或者虚拟网卡无法开启。我还试了nekoray开启TUN模式也不能上网。TUN模式还不成熟。还有v2rayN 6.31版本对Hysteria2类型的节点无法测速。

Hysteria2测速会解决的，需要时间

2dust avatar Dec 25 '23 08:12 2dust

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.

image

另外 就像我上面提到的 其实如果用默认的DNS的话 我这儿的tun是可以使用的（虽然DNS会有问题，但是我看了默认的dns配置，好像又没啥问题），只是不论直连还是代理都会被统计到proxy的网速和流量统计中 。（如果是自己用命令行手动运行singbox的话，还真分辨不出到底配置好没，因为至少能将就用 ） 至于上面提到的情况2还是存在 .

考不考虑加个导入外部config.json配置的选项？有时候图方便在外部改了DNS或者是一些没有经V2rayN里图形化 的配置 等打开v2rayN后又变成之前的了

Kukuair avatar Dec 26 '23 09:12 Kukuair

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

NSIOISN avatar Dec 26 '23 10:12 NSIOISN

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

把完整配置发出来

2dust avatar Dec 27 '23 09:12 2dust

更新之后打开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.

正确，

2dust avatar Dec 27 '23 09:12 2dust

把完整配置发出来

我使用的就是默认的config

tunConfig.json

如果仅仅使用sing box作为内核而不启动tun的话，是没有这些DNS error的。

NSIOISN avatar Dec 27 '23 14:12 NSIOISN

把完整配置发出来

我使用的就是默认的config

tunConfig.json

如果仅仅使用sing box作为内核而不启动tun的话，是没有这些DNS error的。

不是tunconfig.json，6.31在开启tun后路由规则会从v2ray格式自动转换成sing-box格式，应该是开启tun后的config.json，tunconfig.json是6.23的

Kukuair avatar Dec 27 '23 23:12 Kukuair

tunConfig.json 在6.31已经废弃了 需要查看的是config.json @NSIOISN

2dust avatar Dec 28 '23 02:12 2dust

tunConfig.json 在6.31已经废弃了 需要查看的是config.json @NSIOISN

抱歉，这份是我开启tun后的配置，仅去除了server name config.json

作为对比，这是仅用sing box内核不开启tun的配置 config.json

NSIOISN avatar Dec 28 '23 10:12 NSIOISN

tunConfig.json 在6.31已经废弃了 需要查看的是config.json @NSIOISN

抱歉，这份是我开启tun后的配置，仅去除了server name config.json

作为对比，这是仅用sing box内核不开启tun的配置 config.json

从config上看并没有什么问题 等是否有人能看出问题吧

2dust avatar Dec 29 '23 10:12 2dust

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

MrSaeid007 avatar Dec 31 '23 06:12 MrSaeid007

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? 2023-12-31_18-05-41

Seems like there is something wrong with DNS address.

babaksh avatar Dec 31 '23 14:12 babaksh

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? 2023-12-31_18-05-41

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.

MrSaeid007 avatar Dec 31 '23 14:12 MrSaeid007

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? 2023-12-31_18-05-41 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!

babaksh avatar Dec 31 '23 14:12 babaksh

我更新到6.32还是一样的问题，感觉没变啊

wong-hao avatar Jan 02 '24 13:01 wong-hao

我更新到6.32还是一样的问题，感觉没变啊

在tun设置中打开strict route试试

Kukuair avatar Jan 02 '24 14:01 Kukuair

I updated to 6.32 and still have the same problem. I feel the same.

Try turning off ipv6 in Tun settings and check

MrSaeid007 avatar Jan 02 '24 21:01 MrSaeid007

我更新到6.32还是一样的问题，感觉没变啊

在tun设置中打开strict route试试

默认开着的，不是这个问题

wong-hao avatar Jan 04 '24 05:01 wong-hao

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.

wong-hao avatar Jan 04 '24 05:01 wong-hao

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"
}

IMXeno123 avatar Jan 18 '24 17:01 IMXeno123

@2dust 问题已修复，修改配置由 "address": "tcp://8.8.8.8", -> 修改为 "address": "udp://8.8.8.8",即可（反正vmess是可以用的）

lingszz avatar Jan 23 '24 08:01 lingszz

@2dust 问题已修复，修改配置由 "address": "tcp://8.8.8.8", -> 修改为 "address": "udp://8.8.8.8",即可（反正vmess是可以用的）

谢谢反馈，您这个服务器特殊吧，一般都支持默认的DNS

2dust avatar Jan 23 '24 10:01 2dust

@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驱动解决这个问题

lingszz avatar Jan 24 '24 10:01 lingszz

版本：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

Har-JA avatar Feb 18 '24 09:02 Har-JA

版本：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

lingszz avatar Feb 20 '24 08:02 lingszz