search

2dust / v2rayN

A GUI client for Windows, support Xray core and v2fly core and others
https://1.2345345.xyz
GNU General Public License v3.0
64.92k stars 10.97k forks source link

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

Open 2dust opened 7 months ago

2dust commented 7 months ago 
- 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"
}
CodingMoeButa commented 3 months ago

6.43 版本启用TUN模式，系统中没有出现对应的虚拟网卡。

myrshfrs commented 2 months ago

贴一下自己的sing-box DNS设置-Tun模式设置，跟上面的区别在于address_resolver的出站选择proxy，防止dns污染，现在这个配置Tun开启没有问题。 我的系统是：

版本 Windows 11 企业版 版本 21H2 安装日期 ‎2023/‎12/‎16 操作系统版本 22000.2836 体验 Windows 功能体验包 1000.22001.1000.0

v2rayn版本是：V6.43 Tun模式设置：

Strict Mode: true Stack: gvisor mtu: 9000 其他：false

{
"servers": [
{
"tag": "remote",
"address": "https://doh.apad.pro/dns-query",
"address_resolver": "dns-resolver",
"strategy": "ipv4_only",
"detour": "proxy"
},
{
"tag": "local",
"address": "https://dns.pub/dns-query",
"address_resolver": "dns-resolver",
"strategy": "ipv4_only",
"detour": "direct"
},
{
"tag": "block",
"address": "rcode://success"
},
{
"tag": "dns-resolver",
"address": "tcp://8.8.8.8",
"strategy": "ipv4_only",
"detour": "proxy"
}
],
"rules": [
{
"rule_set": [
"geosite-category-ads-all"
],
"server": "block"
},
{
"rule_set": [
"geosite-geolocation-cn"
],
"server": "local"
},
{
"rule_set": [
"geosite-geolocation-!cn"
],
"server": "remote"
}
]
}
Eyion commented 2 months ago

开启tun模式经常魔法失败，不知道是设置问题、线路问题还是软件问题。 需求是该走魔法的走魔法，直连的走直连，全局代理是指所有流量走魔法（没理解错吧），想问下有同样需求的稳定魔法的设置方法。

myrshfrs commented 2 months ago

开启tun模式经常魔法失败，不知道是设置问题、线路问题还是软件问题。 需求是该走魔法的走魔法，直连的走直连，全局代理是指所有流量走魔法（没理解错吧），想问下有同样需求的稳定魔法的设置方法。

我现在用tun没什么问题，你可以先用代理模式看看你的线路稳不稳定，然后切换成tun模式

Eyion commented 2 months ago

tun模式就是魔法和直连流量会分开走的？开了之后，旁边的“系统代理”和“路由”怎么选的，我的总是真连接延迟-1

myrshfrs commented 2 months ago

tun模式就是魔法和直连流量会分开走的？开了之后，旁边的“系统代理”和“路由”怎么选的，我的总是真连接延迟-1

tun模式也是根据你的路由设置的呀，我现在是V2-绕过大陆(Whitelist)，就是分开走的，如果你选择V2-全局(Global)就是全部流量走魔法。 123

Eyion commented 2 months ago

image image 我是这样设置的

myrshfrs commented 2 months ago

image image 我是这样设置的

我建议你把域名解析策略改成：IPIfNonMatch，sing-box域名解析策略改成：prefer_IPv4，然后采用我上面的dns设置，再开启tun试试。

myrshfrs commented 2 months ago

123

{
  "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": [
    {
      "rule_set": [
        "geosite-geolocation-!cn"
      ],
      "server": "remote"
    },
    {
      "rule_set": [
        "geosite-category-ads-all"
      ],
      "server": "block"
    }
  ]
}
{
  "servers": [
    {
      "tag": "remote",
      "address": "https://doh.apad.pro/dns-query",
      "address_resolver": "dns-resolver",
      "strategy": "ipv4_only",
      "detour": "proxy"
    },
    {
      "tag": "local",
      "address": "https://dns.pub/dns-query",
      "address_resolver": "dns-resolver",
      "strategy": "ipv4_only",
      "detour": "direct"
    },
    {
      "tag": "block",
      "address": "rcode://success"
    },
    {
      "tag": "dns-resolver",
      "address": "tcp://8.8.8.8",
      "strategy": "ipv4_only",
      "detour": "proxy"
    }
  ],
  "rules": [
    {
      "rule_set": [
        "geosite-category-ads-all"
      ],
      "server": "block"
    },
    {
      "rule_set": [
        "geosite-geolocation-cn"
      ],
      "server": "local"
    },
    {
      "rule_set": [
        "geosite-geolocation-!cn"
      ],
      "server": "remote"
    }
  ]
}
Eyion commented 2 months ago

好的，谢谢。我是看了油管有个博主视频，改成ASIS的。

Eyion commented 2 months ago

sing-box域名解析策略改成：prefer_IPv4，我咋看你截图是ipv4_only

myrshfrs commented 2 months ago

好的，谢谢。我是看了油管有个博主视频，改成ASIS的。

这是我其他的设置项 123 1234

myrshfrs commented 2 months ago

sing-box域名解析策略改成：prefer_IPv4，我咋看你截图是ipv4_only

我没有ipv6 所以ipv4_only， 如果你也没有，改成ipv4_only也可以

myrshfrs commented 2 months ago

好的，谢谢。我是看了油管有个博主视频，改成ASIS的。

这是我其他的设置项 123 1234

sing-box域名解析策略改成：prefer_IPv4，我咋看你截图是ipv4_only

123 1234

3233177969 commented 2 months ago

好兄弟,还在吗,我的TUN模式开了能用,但是过了一会儿就消失了,就用不了了,是v2rayn的原因吗

keypadDancer commented 2 months ago

好的，谢谢。我是看了油管有个博主视频，改成ASIS的。

这是我其他的设置项 123 1234

sing-box域名解析策略改成：prefer_IPv4，我咋看你截图是ipv4_only

123 1234

服务器真链接延迟-1

winezer0 commented 2 months ago

默认带的sing-box是可以开启tun模式全局的，但是更新sing-box以后就不走代理了，回退以后又能行了。

这是啥问题 6.43版本和之前版本好像都有这个问题

IEXPECTATION commented 2 months ago

当我启动 TUN 模式的时候报出了下面的错误。 initial rule-set: geoip-cn: Get "https://raw.githubusercontent.com/SagerNet/sing-geoip/rule-set/geoip-cn.srs": http2: client connection force closed via ClientConn.Close | initialize rule-set[4]: initial rule-set: geosite-geolocation-!cn: Get "https://raw.githubusercontent.com/SagerNet/sing-geosite/rule-set/geosite-geolocation-!cn.srs": http2: client connection force closed via ClientConn.Close | initialize rule-set[4]: initial rule-set: geosite-geolocation-cn: Get "https://raw.githubusercontent.com/SagerNet/sing-geosite/rule-set/geosite-geolocation-cn.srs": http2: client connection force closed via ClientConn.Close | initialize rule-set[4]: initial rule-set: geosite-category-ads-all: Get "https://raw.githubusercontent.com/SagerNet/sing-geosite/rule-set/geosite-category-ads-all.srs": context canceled | initialize rule-set[4]: initial rule-set: geosite-cn: Get "https://raw.githubusercontent.com/SagerNet/sing-geosite/rule-set/geosite-cn.srs": context canceled 请问，这是我的问题吗？

Rick-Cooper commented 2 months ago

我试了下v6.39的tun模式在我的配置下可用，但是最新的稳定版就友不可用了 有时候报错DNS回环 可以回退下v6.39版本试一试 配置什么的都没有变

Suzhelan commented 1 month ago

在我启动tun模式时出现以下错误 v6.45 FATAL[0000] start service: initialize rule-set[4]: initial rule-set: geoip-cn: Get "https://raw.githubusercontent.com/SagerNet/sing-geoip/rule-set/geoip-cn.srs": unexpected HTTP response status: 404 | initialize rule-set[4]: initial rule-set: geosite-geolocation-cn: Get "https://raw.githubusercontent.com/SagerNet/sing-geosite/rule-set/geosite-geolocation-cn.srs": context canceled | initialize rule-set[4]: initial rule-set: geosite-geolocation-!cn: Get "https://raw.githubusercontent.com/SagerNet/sing-geosite/rule-set/geosite-geolocation-!cn.srs": context canceled | initialize rule-set[4]: initial rule-set: geosite-cn: Get "https://raw.githubusercontent.com/SagerNet/sing-geosite/rule-set/geosite-cn.srs": context canceled | initialize rule-set[4]: initial rule-set: geosite-category-ads-all: Get "https://raw.githubusercontent.com/SagerNet/sing-geosite/rule-set/geosite-category-ads-all.srs": context canceled

LauJennery commented 1 month ago

image 只能无线网，不能有线连接，啥原因

2dust commented 1 month ago

https://github.com/2dust/v2rayN/releases/tag/6.48

rocketraccooo-n commented 4 weeks ago

如果我理解的不错的话，Xray 的DNS流程中，总是先处理国内IP和域名，然后把剩下的发给代理：

    "servers": [
      {
        "address": "223.5.5.5",
        "domains": [
          "geosite:cn",
          "geosite:geolocation-cn"
        ],
        "expectIPs": [
          "geoip:cn"
        ]
      },
      "1.1.1.1",
      "8.8.8.8",
      "https://dns.google/dns-query"
    ]

然后经过一定的测试，发现 geoip/geosite 似乎是有个大坑点，那就是 geosite:geolocation-cn 和 geosite:geolocation-!cn 根本不是补集关系，部分 Google 域名会因为这个给送到国内去。geosite:cn 似乎会在前面的基础上再增加一些国内域名。 注意到这点之后，似乎就可以用以下的 sing-box DNS 极简设置来改善DNS问题：

{
  "servers": [
    {
      "tag": "remote",
      "address": "8.8.8.8",
      "strategy": "ipv4_only",
      "detour": "proxy"
    },
    {
      "tag": "local",
      "address": "dhcp://auto"
    }
  ],
  "rules": [
    {
      "rule_set": [
        "geosite-cn",
        "geosite-geolocation-cn"
      ],
      "server": "local"
    }
  ]
}

由于 remote 被列在第一个，就会作为没有匹配国内时候的默认DNS。 edit: 6.48 里作者好像把 sniff_override_destination 关掉了，想要测试上面的配置得回到 6.45

MrL2020 commented 3 weeks ago

开启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虚拟网卡。不知以上报错如何解决，请求帮助，谢谢！

keypadDancer commented 3 weeks ago

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

keypadDancer commented 3 weeks ago

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

大佬解决了吗

good-bay commented 3 weeks ago

不想折腾了，换客户端了。但是也是不能用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 https://github.com/2dust/v2rayN/issues/4539#issuecomment-2208050089, or unsubscribe https://github.com/notifications/unsubscribe-auth/BD3XBYBRHTTGSQAMPT3ST3LZKS63BAVCNFSM6AAAAABBBMO7R2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBYGA2TAMBYHE . You are receiving this because you are subscribed to this thread.Message ID: @.***>

2dust commented 3 weeks ago

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

Rick-Cooper commented 3 weeks ago

不想折腾了，换客户端了。但是也是不能用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 commented 2 weeks ago

https://github.com/2dust/v2rayN/issues/5308#issuecomment-2210941227

alphires1 commented 2 weeks ago

#5308 (comment)

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

ZZXIXI commented 2 weeks ago

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

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

8W-Fan commented 2 weeks ago

您好！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 commented 2 weeks ago

开了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 commented 2 weeks ago

开了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 commented 2 weeks ago

开了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 commented 2 weeks ago

开了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 commented 2 weeks ago

开了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发起并且疯狂发送。总之非常感谢你的回复。

8W-Fan commented 1 week ago

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