Windows10下Netbird Service会闪退

[Seacity976]

首先，在C:\ProgramData\Netbird目录下的日志文件client.log并没有记录到任何报错，大概在运行了1个多小时后，似乎就是莫名其妙的闪退。

然后托盘里面的软件disconnect再也没有反应，网络连接里面的wt0也消失了，尝试过将wt0改成seacity0后现象还是会有。必须要调用netbird service start后才能再用。
这是日志的最后几行

[Seacity976]

顺带一提，Windows下用的是最新的0.26.7版本

[bcmmbaga]

Hello @Seacity976, could you please share the log files and the output of netbird status -d?

[Seacity976]

你好@Seacity976，您能分享一下日志文件和输出吗netbird status -d？
你好，输出这个，在我尝试netbird service start后，又可以短暂工作1小时，然后服务又停止了

Error: failed to connect to daemon error: context deadline exceeded
If the daemon is not running please run:
netbird service install
netbird service start

[Seacity976]

你好@Seacity976，您能分享一下日志文件和输出吗netbird status -d？

日志文件最后几行，是一个小时前的了

[bcmmbaga]

Please share the entire log file and not screenshots. You can mask any sensitive information such as IP addresses, domains, etc

[Seacity976]

请分享整个日志文件，而不是屏幕截图。您可以屏蔽任何敏感信息，例如 IP 地址、域等

好的，我删掉了一些ip之类的，日志如下：
2024-04-03T13:53:16+08:00 INFO client/cmd/service_controller.go:24: starting Netbird service
2024-04-03T13:53:16+08:00 INFO client/cmd/service_controller.go:64: started daemon server: 127.0.0.1:41731
2024-04-03T13:53:16+08:00 INFO client/internal/connect.go:96: starting NetBird client version 0.26.7
2024-04-03T13:53:19+08:00 INFO client/internal/routemanager/manager.go:76: Routing setup complete
2024-04-03T13:53:20+08:00 INFO signal/client/grpc.go:158: connected to the Signal Service stream
2024-04-03T13:53:20+08:00 INFO client/internal/connect.go:239: Netbird engine started, my IP is: x.x.x.x/16
2024-04-03T13:53:20+08:00 INFO management/client/grpc.go:147: connected to the Management Service stream
2024-04-03T13:53:20+08:00 WARN client/internal/engine.go:498: running SSH server is not permitted
2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.110.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.0.0/18 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.21.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.100.0/24 has not been assigned a routing peer as no peers from the list [+fL5l8=] are currently connected
2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.23.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.25.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:20+08:00 INFO client/internal/dns/host_windows.go:149: added 1 match domains to the state. Domain list: [.netbird.cloud]
2024-04-03T13:53:20+08:00 INFO client/internal/dns/host_windows.go:176: updated the search domains in the registry with 1 domains. Domain list: [netbird.cloud]
2024-04-03T13:53:20+08:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 0s, total rules count: 2
2024-04-03T13:53:23+08:00 INFO client/internal/peer/conn.go:379: connected to peer , endpoint address: x.x.x.x:49961
2024-04-03T13:53:23+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxx with peer with score 2 for network 172.31.23.0/24
2024-04-03T13:53:23+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxx with peer with score 2 for network 192.168.110.0/24
2024-04-03T13:53:23+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxx with peer with score 2 for network 172.31.21.0/24
2024-04-03T13:53:23+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxx with peer with score 2 for network 192.168.0.0/18
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 INFO client/internal/peer/conn.go:379: connected to peer +fL5l8=, endpoint address: x.x.x.x:51820
2024-04-03T13:53:24+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxx with peer +fL5l8= with score 2 for network 192.168.100.0/24
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 INFO client/internal/peer/conn.go:379: connected to peer , endpoint address: x.x.x.x:16450
2024-04-03T13:53:24+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxx with peer with score 2 for network 172.31.25.0/24
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 172.31.21.0/24: remove route: get peer state: peer not found
2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 172.31.23.0/24: remove route: get peer state: peer not found
2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 192.168.110.0/24: remove route: get peer state: peer not found
2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 172.31.25.0/24: remove route: get peer state: peer not found
2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 192.168.100.0/24: remove route: get peer state: peer not found
2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 192.168.0.0/18: remove route: get peer state: peer not found
2024-04-03T13:53:27+08:00 INFO client/internal/routemanager/manager.go:98: Routing cleanup complete
2024-04-03T13:53:27+08:00 INFO client/internal/engine.go:220: stopped Netbird Engine
2024-04-03T13:53:27+08:00 INFO client/internal/connect.go:253: stopped NetBird client
2024-04-03T13:53:53+08:00 INFO client/internal/connect.go:96: starting NetBird client version 0.26.7
2024-04-03T13:53:55+08:00 INFO client/internal/routemanager/manager.go:76: Routing setup complete
2024-04-03T13:53:56+08:00 INFO signal/client/grpc.go:158: connected to the Signal Service stream
2024-04-03T13:53:56+08:00 INFO client/internal/connect.go:239: Netbird engine started, my IP is: x.x.x.x/16
2024-04-03T13:53:57+08:00 INFO management/client/grpc.go:147: connected to the Management Service stream
2024-04-03T13:53:57+08:00 WARN client/internal/engine.go:498: running SSH server is not permitted
2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.100.0/24 has not been assigned a routing peer as no peers from the list [+fL5l8=] are currently connected
2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.25.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.23.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.0.0/18 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.110.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.21.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:57+08:00 INFO client/internal/dns/host_windows.go:149: added 1 match domains to the state. Domain list: [.netbird.cloud]
2024-04-03T13:53:57+08:00 INFO client/internal/dns/host_windows.go:176: updated the search domains in the registry with 1 domains. Domain list: [netbird.cloud]
2024-04-03T13:53:57+08:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 0s, total rules count: 2
2024-04-03T13:54:00+08:00 INFO client/internal/peer/conn.go:379: connected to peer +fL5l8=, endpoint address: x.x.x.x:51820
2024-04-03T13:54:00+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxxxx with peer +fL5l8= with score 2 for network 192.168.100.0/24
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 INFO client/internal/peer/conn.go:379: connected to peer , endpoint address: x.x.x.x:16450
2024-04-03T13:54:00+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxx with peer with score 2 for network 172.31.25.0/24
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 INFO client/internal/peer/conn.go:379: connected to peer , endpoint address: x.x.x.x:49961
2024-04-03T13:54:01+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxx with peer with score 2 for network 192.168.110.0/24
2024-04-03T13:54:01+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxx with peer with score 2 for network 192.168.0.0/18
2024-04-03T13:54:01+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxx with peer with score 2 for network 172.31.21.0/24
2024-04-03T13:54:01+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxx with peer with score 2 for network 172.31.23.0/24
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:45+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.100.0/24 has not been assigned a routing peer as no peers from the list [+fL5l8=] are currently connected
2024-04-03T14:52:48+08:00 INFO client/internal/peer/conn.go:379: connected to peer +fL5l8=, endpoint address: x.x.x.x:51820
2024-04-03T14:52:48+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is co5vub3xxxxxxxxxxxx with peer +fL5l8= with score 2 for network 192.168.100.0/24
2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:53+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.25.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T14:52:55+08:00 INFO client/internal/peer/conn.go:379: connected to peer , endpoint address: x.x.x.x:16450
2024-04-03T14:52:55+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is co5vub3xxxxxxxxxxxx with peer with score 2 for network 172.31.25.0/24
2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:53:02+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.21.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T14:53:02+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.23.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T14:53:02+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.110.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T14:53:02+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.0.0/18 has not been assigned a routing peer as no peers from the list [] are currently connected

[bcmmbaga]

Did this happen after upgrading to v0.26.7?

[Seacity976]

Did this happen after upgrading to v0.26.7?

0.26.6也会，正是如此，我升级到0.6.27，问题还是存在

[lixmal]

The errors are harmless, this should be fixed with 0.27.0, can you test with that version?