Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
2dust opened this issue Dec 24, 2023 · 97 comments
Open

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

2dust opened this issue Dec 24, 2023 · 97 comments
Labels
help wanted Extra attention is needed

Comments

@2dust
Copy link
Owner

2dust commented Dec 24, 2023

v6.50 开始,Tun模式的启动内核已经有新的模式

  • 使用sing-box core时只运行一个core;
  • 使用非sing-box core时,将使用sing-box额外启动一个前置Socks服务,提供tun入口,此时运行两个core
- 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 2dust added the help wanted Extra attention is needed label Dec 24, 2023
@2dust 2dust pinned this issue Dec 24, 2023
@good-bay
Copy link

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

@X-Oracle
Copy link

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

@Kukuair
Copy link

Kukuair commented Dec 24, 2023

@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
Copy link

Kukuair commented Dec 24, 2023

我的情况是:

  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) 中 enableExInbound 对应函数的问题?(不过不管是true还是false都会卡死,可能也不是这儿的问题,这里只是怀疑)
    image

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

@2dust
Copy link
Owner Author

2dust commented Dec 25, 2023

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

@2dust
Copy link
Owner Author

2dust commented Dec 25, 2023

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

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

@Kukuair
Copy link

Kukuair commented Dec 26, 2023

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后又变成之前的了

@NSIOISN
Copy link

NSIOISN commented Dec 26, 2023

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
Copy link
Owner Author

2dust commented Dec 27, 2023

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
Copy link
Owner Author

2dust commented Dec 27, 2023

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

正确,

@NSIOISN
Copy link

NSIOISN commented Dec 27, 2023

把完整配置发出来

我使用的就是默认的config

tunConfig.json

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

@Kukuair
Copy link

Kukuair commented Dec 27, 2023

把完整配置发出来

我使用的就是默认的config

tunConfig.json

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

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

@2dust
Copy link
Owner Author

2dust commented Dec 28, 2023

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

@NSIOISN
Copy link

NSIOISN commented Dec 28, 2023

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

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

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

@2dust
Copy link
Owner Author

2dust commented Dec 29, 2023

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

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

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

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

@MrSaeid007
Copy link

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

#4012 has been resolved. Thank you @2dust

@babaksh
Copy link

babaksh commented Dec 31, 2023

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.

@MrSaeid007
Copy link

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.

@babaksh
Copy link

babaksh commented Dec 31, 2023

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!

@wong-hao
Copy link

wong-hao commented Jan 2, 2024

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

@Kukuair
Copy link

Kukuair commented Jan 2, 2024

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

在tun设置中打开strict route试试

@MrSaeid007
Copy link

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

Try turning off ipv6 in Tun settings and check

@wong-hao
Copy link

wong-hao commented Jan 4, 2024

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

在tun设置中打开strict route试试

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

@wong-hao
Copy link

wong-hao commented Jan 4, 2024

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.

@IMXeno123
Copy link

IMXeno123 commented Jan 18, 2024

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

@lingszz
Copy link

lingszz commented Jan 23, 2024

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

@MrL2020
Copy link

MrL2020 commented Jul 2, 2024

开启tun后日志报错如下:
+0800 2024-07-03 00:21:15 ERROR dns: exchange failed for www.gstatic.com. IN A: context canceled
+0800 2024-07-03 00:21:15 ERROR dns: exchange failed for www.gstatic.com. IN A: context canceled
+0800 2024-07-03 00:21:20 ERROR [3020462152 1ms] inbound/tun[tun-in]: socks5: request rejected, code=7
+0800 2024-07-03 00:21:22 ERROR [3201676718 4ms] inbound/tun[tun-in]: socks5: request rejected, code=7
+0800 2024-07-03 00:21:43 ERROR [1116360665 4ms] inbound/tun[tun-in]: socks5: request rejected, code=7
网络适配器能看到singbox_tun虚拟网卡。不知以上报错如何解决,请求帮助,谢谢!

@pinecone-squirrel
Copy link

打开tun模式cpu占用率直接飙到100%

@pinecone-squirrel
Copy link

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

大佬解决了吗

@good-bay
Copy link

good-bay commented Jul 4, 2024 via email

@2dust
Copy link
Owner Author

2dust commented Jul 5, 2024

Tun模式确实在很多设备上有问题,实在不行换个app是不错的办法

@Rick-Cooper
Copy link

不想折腾了,换客户端了。但是也是不能用TUN模式的,nekobox keypadDancer @.> 于 2024年7月4日周四 11:32写道:

我这里windows 10 无论何版本都不能开启TUN模式上网,不是断网就是DNS无法解析或者虚拟网卡无法开启。我还试了nekoray开启TUN模式也不能上网。TUN模式还不成熟。还有v2rayN 6.31版本对Hysteria2类型的节点无法测速。 大佬解决了吗 — Reply to this email directly, view it on GitHub <#4539 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BD3XBYBRHTTGSQAMPT3ST3LZKS63BAVCNFSM6AAAAABBBMO7R2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBYGA2TAMBYHE . You are receiving this because you are subscribed to this thread.Message ID: @.
>

可以回退到6.39版本试试,内核和规则正常更新,我现在6.39版本tun模式基本上一切正常

@alphires1
Copy link

#5308 (comment)

@alphires1
Copy link

#5308 (comment)

简单一点的解决方案可以参考我这条回复,有精力的可以去一个个测试下再来回复

@ZZXIXI
Copy link

ZZXIXI commented Jul 5, 2024

打开tun模式cpu占用率直接飙到100%

看一下设置里的dns设置把里面的默认设置全删了再试

@8W-Fan
Copy link

8W-Fan commented Jul 8, 2024

您好!Tun模式下进行游戏有时玩一段时间后突然变得比较卡,这时发现sing-box.exe进程占用了大量内存和CPU(30%CPU, 500+MB内存),重启后会恢复正常,但是我不想暴露我的真实IP, 这就得先关了游戏然后重新进,比较麻烦。这个问题大概平均几天就会出现一次。我搜了一下这个问题,似乎是sing-box的tun设置里面udp_timeout值设置的小一些就能解决(我是小白完全不懂这些,不知道这样做到底能不能解决),但是我在v2rayN里面找不到自定义json配置的地方,tun设置里面只支持设置部分选项没有这个udp_timeout。请问v2rayN是否会考虑支持自定义导入sing-box的tun设置呢?DNS设置似乎是可以json自定义的,但是这种tun设置我没有找到。

@8W-Fan
Copy link

8W-Fan commented Jul 10, 2024

开了debug级别的日志并且存到了文件。今天又出现了这个问题,文件大小(49M)明显大于没出问题的昨天时的日志文件(7M)。发现出问题的时候开始大量出现这一种记录:

+0800 2024-07-10 19:32:15 INFO [3914010307 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58481
+0800 2024-07-10 19:32:15 INFO [3914010307 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:15 INFO [3914010307 1ms] router: found process path: C:\Tencent\QQ\Bin\QQ.exe
+0800 2024-07-10 19:32:15 DEBUG [3914010307 1ms] router: match[9] ip_cidr=[223.5.5.5/32 119.29.29.29/32 180.76.76.76/32...] ip_is_private=true rule_set=geoip-cn => direct
+0800 2024-07-10 19:32:15 INFO [3914010307 1ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [4053653661 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58482
+0800 2024-07-10 19:32:16 INFO [4053653661 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [4053653661 0ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [4053653661 0ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [4053653661 30ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58483
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [641947606 0ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [4136645969 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58484
+0800 2024-07-10 19:32:16 INFO [4136645969 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [4136645969 12ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [4136645969 12ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [4136645969 13ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58485
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [4023451841 0ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [2089744284 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58486
+0800 2024-07-10 19:32:16 INFO [2089744284 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [2089744284 1ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [2089744284 1ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [2089744284 1ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [3063098191 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58487
+0800 2024-07-10 19:32:16 INFO [3063098191 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [3063098191 1ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [3063098191 1ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [3063098191 1ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:17 INFO [2915872867 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58488
+0800 2024-07-10 19:32:17 INFO [2915872867 1ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001

240e:97c:2f:1::46这个地址就是在这个时候第一次出现的,从这开始就疯狂地出现这个IP地址。
+0800 2024-07-10 19:32:16 DEBUG [3063098191 1ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
这样的长记录也是这时候才出现的,之前没有。

@wtfr-dot
Copy link

开了debug级别的日志并且存到了文件。今天又出现了这个问题,文件大小(49M)明显大于没出问题的昨天时的日志文件(7M)。发现出问题的时候开始大量出现这一种记录:

+0800 2024-07-10 19:32:15 INFO [3914010307 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58481
+0800 2024-07-10 19:32:15 INFO [3914010307 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:15 INFO [3914010307 1ms] router: found process path: C:\Tencent\QQ\Bin\QQ.exe
+0800 2024-07-10 19:32:15 DEBUG [3914010307 1ms] router: match[9] ip_cidr=[223.5.5.5/32 119.29.29.29/32 180.76.76.76/32...] ip_is_private=true rule_set=geoip-cn => direct
+0800 2024-07-10 19:32:15 INFO [3914010307 1ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [4053653661 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58482
+0800 2024-07-10 19:32:16 INFO [4053653661 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [4053653661 0ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [4053653661 0ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [4053653661 30ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58483
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [641947606 0ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [4136645969 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58484
+0800 2024-07-10 19:32:16 INFO [4136645969 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [4136645969 12ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [4136645969 12ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [4136645969 13ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58485
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [4023451841 0ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [2089744284 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58486
+0800 2024-07-10 19:32:16 INFO [2089744284 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [2089744284 1ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [2089744284 1ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [2089744284 1ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [3063098191 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58487
+0800 2024-07-10 19:32:16 INFO [3063098191 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [3063098191 1ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [3063098191 1ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [3063098191 1ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:17 INFO [2915872867 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58488
+0800 2024-07-10 19:32:17 INFO [2915872867 1ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001

240e:97c:2f:1::46这个地址就是在这个时候第一次出现的,从这开始就疯狂地出现这个IP地址。 +0800 2024-07-10 19:32:16 DEBUG [3063098191 1ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct 这样的长记录也是这时候才出现的,之前没有。

你这个记录看起来是没什么问题,之所以出现这样长的记录,是因为singbox这个进程处于process路由规则的direct里,这里只是一种描述,不是错误信息,你需要注意的是疯狂出现的那个ip,看它是否是合法连接,通过反查看能不能找出是哪个软件发出的,是哪个域名,再结合你自己实际使用看它是否是正常的

@8W-Fan
Copy link

8W-Fan commented Jul 11, 2024

开了debug级别的日志并且存到了文件。今天又出现了这个问题,文件大小(49M)明显大于没出问题的昨天时的日志文件(7M)。发现出问题的时候开始大量出现这一种记录:

+0800 2024-07-10 19:32:15 INFO [3914010307 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58481
+0800 2024-07-10 19:32:15 INFO [3914010307 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:15 INFO [3914010307 1ms] router: found process path: C:\Tencent\QQ\Bin\QQ.exe
+0800 2024-07-10 19:32:15 DEBUG [3914010307 1ms] router: match[9] ip_cidr=[223.5.5.5/32 119.29.29.29/32 180.76.76.76/32...] ip_is_private=true rule_set=geoip-cn => direct
+0800 2024-07-10 19:32:15 INFO [3914010307 1ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [4053653661 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58482
+0800 2024-07-10 19:32:16 INFO [4053653661 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [4053653661 0ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [4053653661 0ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [4053653661 30ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58483
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [641947606 0ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [4136645969 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58484
+0800 2024-07-10 19:32:16 INFO [4136645969 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [4136645969 12ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [4136645969 12ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [4136645969 13ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58485
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [4023451841 0ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [2089744284 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58486
+0800 2024-07-10 19:32:16 INFO [2089744284 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [2089744284 1ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [2089744284 1ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [2089744284 1ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [3063098191 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58487
+0800 2024-07-10 19:32:16 INFO [3063098191 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [3063098191 1ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [3063098191 1ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [3063098191 1ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:17 INFO [2915872867 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58488
+0800 2024-07-10 19:32:17 INFO [2915872867 1ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001

240e:97c:2f:1::46这个地址就是在这个时候第一次出现的,从这开始就疯狂地出现这个IP地址。 +0800 2024-07-10 19:32:16 DEBUG [3063098191 1ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct 这样的长记录也是这时候才出现的,之前没有。

你这个记录看起来是没什么问题,之所以出现这样长的记录,是因为singbox这个进程处于process路由规则的direct里,这里只是一种描述,不是错误信息,你需要注意的是疯狂出现的那个ip,看它是否是合法连接,通过反查看能不能找出是哪个软件发出的,是哪个域名,再结合你自己实际使用看它是否是正常的

感谢回复。这个IP似乎是腾讯的IP, 我在游戏的时候有打开QQ和微信电脑版,可能是这两个软件发出的,但具体是哪个还有待排查。但无论如何不用Tun模式的时候这两个软件不可能会占用这么多的内存(开Tun模式出现这个问题的时候sing-box.exe会占用500多M内存),并且这个连接请求一直是疯狂地发送,仅仅二十多分钟记录的日志就有了40多M大,因此我感觉这不是正常现象。

@wtfr-dot
Copy link

wtfr-dot commented Jul 11, 2024

开了debug级别的日志并且存到了文件。今天又出现了这个问题,文件大小(49M)明显大于没出问题的昨天时的日志文件(7M)。发现出问题的时候开始大量出现这一种记录:

+0800 2024-07-10 19:32:15 INFO [3914010307 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58481
+0800 2024-07-10 19:32:15 INFO [3914010307 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:15 INFO [3914010307 1ms] router: found process path: C:\Tencent\QQ\Bin\QQ.exe
+0800 2024-07-10 19:32:15 DEBUG [3914010307 1ms] router: match[9] ip_cidr=[223.5.5.5/32 119.29.29.29/32 180.76.76.76/32...] ip_is_private=true rule_set=geoip-cn => direct
+0800 2024-07-10 19:32:15 INFO [3914010307 1ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [4053653661 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58482
+0800 2024-07-10 19:32:16 INFO [4053653661 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [4053653661 0ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [4053653661 0ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [4053653661 30ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58483
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [641947606 0ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [4136645969 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58484
+0800 2024-07-10 19:32:16 INFO [4136645969 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [4136645969 12ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [4136645969 12ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [4136645969 13ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58485
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [4023451841 0ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [2089744284 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58486
+0800 2024-07-10 19:32:16 INFO [2089744284 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [2089744284 1ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [2089744284 1ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [2089744284 1ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [3063098191 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58487
+0800 2024-07-10 19:32:16 INFO [3063098191 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [3063098191 1ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [3063098191 1ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [3063098191 1ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:17 INFO [2915872867 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58488
+0800 2024-07-10 19:32:17 INFO [2915872867 1ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001

240e:97c:2f:1::46这个地址就是在这个时候第一次出现的,从这开始就疯狂地出现这个IP地址。 +0800 2024-07-10 19:32:16 DEBUG [3063098191 1ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct 这样的长记录也是这时候才出现的,之前没有。

你这个记录看起来是没什么问题,之所以出现这样长的记录,是因为singbox这个进程处于process路由规则的direct里,这里只是一种描述,不是错误信息,你需要注意的是疯狂出现的那个ip,看它是否是合法连接,通过反查看能不能找出是哪个软件发出的,是哪个域名,再结合你自己实际使用看它是否是正常的

感谢回复。这个IP似乎是腾讯的IP, 我在游戏的时候有打开QQ和微信电脑版,可能是这两个软件发出的,但具体是哪个还有待排查。但无论如何不用Tun模式的时候这两个软件不可能会占用这么多的内存(开Tun模式出现这个问题的时候sing-box.exe会占用500多M内存),并且这个连接请求一直是疯狂地发送,仅仅二十多分钟记录的日志就有了40多M大,因此我感觉这不是正常现象。

这个肯定不正常,还有一个问题,如果是qq或者微信连接的那个ip,照道理应该是qq和wecat这两个进程发起连接,但是现在看起来好像全部由singbox发起了,这块我觉得不正常,至少我这里qq和WeChat都是由客户端自己发起的连接,比如:
+0800 2024-06-27 13:14:41 INFO [1337426501 311ms] router: found process path: E:\Program Files\Tencent\WeChat\WeChat.exe
+0800 2024-06-27 13:14:41 DEBUG [1337426501 311ms] router: match[11] network=[tcp udp] ip_is_private=true rule_set=geoip-cn => direct
+0800 2024-06-27 13:14:41 INFO [1337426501 311ms] outbound/direct[direct]: outbound connection to 183.60.8.74:443
+0800 2024-06-27 13:14:41 INFO [4071104528 481ms] outbound/direct[direct]: outbound packet connection

+0800 2024-06-27 13:14:41 INFO [3557094680 0ms] router: found process path: E:\Program Files (x86)\Tencent\TIM\Bin\TIM.exe
+0800 2024-06-27 13:14:41 DEBUG [3557094680 0ms] router: match[11] network=[tcp udp] ip_is_private=true rule_set=geoip-cn => direct
+0800 2024-06-27 13:14:41 INFO [3557094680 0ms] outbound/direct[direct]: outbound packet connection

你这个情况要大佬们分析一下,我感觉不是v2rayN本身的问题,我这里tun开启singbox只占用60多m内存,xray也只占100多m

@8W-Fan
Copy link

8W-Fan commented Jul 11, 2024

开了debug级别的日志并且存到了文件。今天又出现了这个问题,文件大小(49M)明显大于没出问题的昨天时的日志文件(7M)。发现出问题的时候开始大量出现这一种记录:

+0800 2024-07-10 19:32:15 INFO [3914010307 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58481
+0800 2024-07-10 19:32:15 INFO [3914010307 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:15 INFO [3914010307 1ms] router: found process path: C:\Tencent\QQ\Bin\QQ.exe
+0800 2024-07-10 19:32:15 DEBUG [3914010307 1ms] router: match[9] ip_cidr=[223.5.5.5/32 119.29.29.29/32 180.76.76.76/32...] ip_is_private=true rule_set=geoip-cn => direct
+0800 2024-07-10 19:32:15 INFO [3914010307 1ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [4053653661 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58482
+0800 2024-07-10 19:32:16 INFO [4053653661 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [4053653661 0ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [4053653661 0ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [4053653661 30ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58483
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [641947606 0ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [641947606 0ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [4136645969 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58484
+0800 2024-07-10 19:32:16 INFO [4136645969 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [4136645969 12ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [4136645969 12ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [4136645969 13ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58485
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [4023451841 0ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [4023451841 0ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [2089744284 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58486
+0800 2024-07-10 19:32:16 INFO [2089744284 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [2089744284 1ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [2089744284 1ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [2089744284 1ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:16 INFO [3063098191 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58487
+0800 2024-07-10 19:32:16 INFO [3063098191 0ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001
+0800 2024-07-10 19:32:16 INFO [3063098191 1ms] router: found process path: E:\F\mfaktc-0.21-repunit\v2rayN-With-Core\bin\sing_box\sing-box.exe
+0800 2024-07-10 19:32:16 DEBUG [3063098191 1ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct
+0800 2024-07-10 19:32:16 INFO [3063098191 1ms] outbound/direct[direct]: outbound packet connection
+0800 2024-07-10 19:32:17 INFO [2915872867 0ms] inbound/tun[tun-in]: inbound packet connection from [fdfe:dcba:9876::1]:58488
+0800 2024-07-10 19:32:17 INFO [2915872867 1ms] inbound/tun[tun-in]: inbound packet connection to [240e:97c:2f:1::46]:8001

240e:97c:2f:1::46这个地址就是在这个时候第一次出现的,从这开始就疯狂地出现这个IP地址。 +0800 2024-07-10 19:32:16 DEBUG [3063098191 1ms] router: match[3] process_name=[wv2ray.exe v2ray.exe SagerNet.exe v2ray.exe v2ray.exe xray.exe wxray.exe clash-windows-amd64-v3.exe clash-windows-amd64.exe clash-windows-386.exe clash.exe Clash.Meta-windows-amd64-compatible.exe Clash.Meta-windows-amd64.exe Clash.Meta-windows-386.exe Clash.Meta.exe clash.exe mihomo-windows-amd64.exe mihomo-windows-amd64-compatible.exe mihomo-windows-amd64.exe mihomo-windows-386.exe mihomo.exe clash.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe naiveproxy.exe naive.exe tuic-client.exe tuic.exe sing-box-client.exe sing-box.exe juicity-client.exe juicity.exe hysteria-windows-amd64.exe hysteria-windows-386.exe hysteria.exe] => direct 这样的长记录也是这时候才出现的,之前没有。

你这个记录看起来是没什么问题,之所以出现这样长的记录,是因为singbox这个进程处于process路由规则的direct里,这里只是一种描述,不是错误信息,你需要注意的是疯狂出现的那个ip,看它是否是合法连接,通过反查看能不能找出是哪个软件发出的,是哪个域名,再结合你自己实际使用看它是否是正常的

感谢回复。这个IP似乎是腾讯的IP, 我在游戏的时候有打开QQ和微信电脑版,可能是这两个软件发出的,但具体是哪个还有待排查。但无论如何不用Tun模式的时候这两个软件不可能会占用这么多的内存(开Tun模式出现这个问题的时候sing-box.exe会占用500多M内存),并且这个连接请求一直是疯狂地发送,仅仅二十多分钟记录的日志就有了40多M大,因此我感觉这不是正常现象。

这个肯定不正常,还有一个问题,如果是qq或者微信连接的那个ip,照道理应该是qq和wecat这两个进程发起连接,但是现在看起来好像全部由singbox发起了,这块我觉得不正常,至少我这里qq和WeChat都是由客户端自己发起的连接,比如: +0800 2024-06-27 13:14:41 INFO [1337426501 311ms] router: found process path: E:\Program Files\Tencent\WeChat\WeChat.exe +0800 2024-06-27 13:14:41 DEBUG [1337426501 311ms] router: match[11] network=[tcp udp] ip_is_private=true rule_set=geoip-cn => direct +0800 2024-06-27 13:14:41 INFO [1337426501 311ms] outbound/direct[direct]: outbound connection to 183.60.8.74:443 +0800 2024-06-27 13:14:41 INFO [4071104528 481ms] outbound/direct[direct]: outbound packet connection

+0800 2024-06-27 13:14:41 INFO [3557094680 0ms] router: found process path: E:\Program Files (x86)\Tencent\TIM\Bin\TIM.exe +0800 2024-06-27 13:14:41 DEBUG [3557094680 0ms] router: match[11] network=[tcp udp] ip_is_private=true rule_set=geoip-cn => direct +0800 2024-06-27 13:14:41 INFO [3557094680 0ms] outbound/direct[direct]: outbound packet connection

你这个情况要大佬们分析一下,我感觉不是v2rayN本身的问题,我这里tun开启singbox只占用60多m内存,xray也只占100多m

又看了一下上面的我的记录,第一次连接发起的时候([fdfe:dcba:9876::1]:58481那次)好像是QQ发起的,之后(58482开始)就变成sing-box了,并且是疯狂地发起请求。之后又出现了类似的一些请求,也是这个样子,一开始QQ发起,然后变成了sing-box发起并且疯狂发送。总之非常感谢你的回复。

@2dust 2dust mentioned this issue Jul 12, 2024
2 tasks
@8W-Fan
Copy link

8W-Fan commented Jul 12, 2024

#5308
您好,请问您是指的这个issue吗?我是小白,抱歉看不明白您提到的那个issue. 我是大概5月底下载的v2rayN的全新的版本用的,从那开始就有这个问题,然后更新到6.49以及现在的6.50仍然还有。至于避免的话,既然已经排查出来是QQ的问题了,现在我把QQ关了应该不会再遇到这个问题了(至少这两天没再出现,仍然在继续观察)。我是正常的win10家用电脑,网络方面应该没进行什么特殊的设置,虽然可以避免了但是个人还是希望找出问题所在,比如是不是配置方面的问题或者什么bug。

@APT-ZERO
Copy link

I run sing-tun manually and there is no problem, but v2rayN don't turn it on itself for xray custom json configs

@BlackNorton
Copy link

Run v2rayN with naiveproxy core, had the same problem, but it's solved now by turn off "strict route" in tun mode setting

@APT-ZERO
Copy link

APT-ZERO commented Aug 5, 2024

Good news is that Xray-core want to add Tun inbound XTLS/Xray-core#3576
If you want v2rayN Tun problem get solved, you can ask the Core devs instead of v2rayN dev

@lingszz
Copy link

lingszz commented Aug 29, 2024

开启tun后日志报错如下: +0800 2024-07-03 00:21:15 ERROR dns: exchange failed for www.gstatic.com. IN A: context canceled +0800 2024-07-03 00:21:15 ERROR dns: exchange failed for www.gstatic.com. IN A: context canceled +0800 2024-07-03 00:21:20 ERROR [3020462152 1ms] inbound/tun[tun-in]: socks5: request rejected, code=7 +0800 2024-07-03 00:21:22 ERROR [3201676718 4ms] inbound/tun[tun-in]: socks5: request rejected, code=7 +0800 2024-07-03 00:21:43 ERROR [1116360665 4ms] inbound/tun[tun-in]: socks5: request rejected, code=7 网络适配器能看到singbox_tun虚拟网卡。不知以上报错如何解决,请求帮助,谢谢!

#5595 DNS的报错可以尝试删除"tcp://"

@Lycofuture
Copy link

Lycofuture commented Aug 30, 2024

均衡负载/最低延迟 使用tun模式无法使用ipv6,即使设置里打开了也用不了,关闭tun模式可以使用ipv6。版本是v6.55
yaml订阅的custom类型的ipv6始终是或内的ip
版本是 v6.55

@codemanwg
Copy link

我把热点关了就可以用了

@miaozilong
Copy link

我现在想用负载均衡(新版本)和TUN(老版本) 怎么办?

@miaozilong
Copy link

我已经试过了把老版本sing-box.exe复制到新版本中 还是不行。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests