vernesong/OpenClash

[Bug] 断电重启后，无法dns和连接

NoNameCanUse9 opened this issue · 2 comments

NoNameCanUse9 commented

Verify Steps

  • Tracker 我已经在 Issue Tracker 中找过我要提出的问题
  • Branch 我知道 OpenClash 的 Dev 分支切换开关位于插件设置-版本更新中，或者我会手动下载并安装 Dev 分支的 OpenClash
  • Latest 我已经使用最新 Dev 版本测试过，问题依旧存在
  • Relevant 我知道 OpenClash 与 内核(Core)、控制面板(Dashboard)、在线订阅转换(Subconverter)等项目之间无直接关系，仅相互调用
  • Definite 这确实是 OpenClash 出现的问题
  • Contributors 我有能力协助 OpenClash 开发并解决此问题
  • Meaningless 我提交的是无意义的催促更新或修复请求

OpenClash Version

v0.46.014-beta

Bug on Environment

Istoreos

OpenWrt Version

iStoreOS 22.03.7 2024080210

Bug on Platform

Linux-arm64

Describe the Bug

我跳闸之后，来电重启一段时间之后，就一直dns解析不了，无论经不经过adg，重新启动后也是不行 。

To Reproduce

断电重启后， 重新启动clash 稳定复现

OpenClash Log

2024-08-25 23:14:35 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🚀 节点选择 
2024-08-25 23:14:35 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=📲 电报消息
2024-08-25 23:14:33 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🚀 节点选择 
2024-08-25 23:14:33 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🐟 漏网之鱼
2024-08-25 23:14:33 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🐟 漏网之鱼 
2024-08-25 23:14:33 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🚀 节点选择
2024-08-25 23:14:31 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🐟 漏网
2024-08-25 23:14:31 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🐟 漏网之鱼 lAddr=192.168.100.184:8569 rAddr=doh.dns.sb:443 rule=Match rulePayload=
2024-08-25 23:14:31 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🚀 节点选择 
2024-08-25 23:14:31 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🚀 节点选择 l
2024-08-25 23:14:31 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🐟 漏网之鱼 lAddr=192.168.100.184:8564 rAddr=8.8.4.4:853 rule=Match rulePayload=
2024-08-25 23:14:31 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🐟 漏网之鱼 
2024-08-25 23:14:31 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🐟 漏网之鱼 
2024-08-25 23:14:31 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🚀 节点选择
2024-08-25 23:14:31 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=📲 电报消息
2024-08-25 23:14:31 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=📲 电报消息 l
2024-08-25 23:14:29 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🐟 漏网之鱼 
2024-08-25 23:14:29 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🚀 节点选择rAddr=android.clients.google.com:443 rule=DomainKeyword rulePayload=google
2024-08-25 23:14:29 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🐟 漏网之鱼
2024-08-25 23:14:29 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🐟 漏网之鱼
2024-08-25 23:14:29 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=🚀 节点选择
2024-08-25 23:14:27 WRN [TCP] dial failed error=jp01.goodyun.buzz:35584 connect error: dial tcp4 42.180.125.99:35584: i/o timeout proxy=📲 电报消息

OpenClash Config

No response

Expected Behavior

能正常dns解析

Additional Context

No response

NoNameCanUse9 commented

image

感谢，作者！ 这问题困扰我几个月了，翻了好久issuse也没有找到方法，现在终于解决了。