We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.46.050 beta
Istoreos
固件版本 iStoreOS 22.03.7 2024102509 内核版本 5.10.221
Linux-amd64(x86-64)
现在所有的调试方式都试了,现在的情况是有节点Ping,但是实际没有任何流量通过openclash。我测试了两个机场。之前上一个版本是正常的。我使用的是固件版本 iStoreOS 22.03.7 2024102509 内核版本 5.10.221 但是客户端clashx和安卓版的都可以用
2024-11-21 20:29:56 OpenClash 启动成功,请等待服务器上线! 2024-11-21 20:29:56 第七步: 添加计划任务,启动进程守护程序... 2024-11-21 20:29:56 提示:开始添加自定义防火墙规则... 2024-11-21 20:29:56 提示:正在根据防火墙端口转发和防火墙通信规则添加端口绕过规则... 2024-11-21 20:29:55 提示:DNS 劫持模式为防火墙转发... 2024-11-21 20:29:55 第六步: 设置防火墙规则... 2024-11-21 20:29:52 第五步: 设置 Dnsmasq 程序... 2024-11-21 20:29:52 配置文件【/etc/openclash/白月光.yaml】测试成功... 2024-11-21 20:29:51 启动前调用内核测试配置文件... 2024-11-21 20:29:51 第四步: 启动主程序... 2024-11-21 20:29:51 提示:开始运行自定义覆写脚本... 2024-11-21 20:29:50 提示:为保证绕过 IP 正常工作,已在 Fake-IP-Filter 中添加规则【geosite:cn】... 2024-11-21 20:29:49 第三步: 修改配置文件... 2024-11-21 20:29:49 第二步: 组件运行前检查... 2024-11-21 20:29:48 第一步: 获取配置... 2024-11-21 20:29:48 OpenClash 开始启动... 2024-11-21 20:29:48 OpenClash 关闭成功! 2024-11-21 20:29:48 第六步:删除 OpenClash 残留文件... 2024-11-21 20:29:45 第五步: 重启 Dnsmasq 程序... 2024-11-21 20:29:45 第四步: 关闭 Clash 主程序... 2024-11-21 20:29:45 第三步: 关闭 OpenClash 守护程序... 2024-11-21 20:29:45 第二步: 删除 OpenClash 防火墙规则... 2024-11-21 20:29:45 第一步: 备份当前策略组状态... 2024-11-21 20:29:45 OpenClash 开始关闭... 2024-11-21 20:29:45 OpenClash 重新启动中...
2024-11-21 20:29:53 level=info msg="Load MMDB file: /etc/openclash/Country.mmdb" 2024-11-21 20:29:53 level=info msg="UI already exists, skip downloading" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 📺 巴哈姆特" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🐟 漏网之鱼" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider ♻️ 自动选择" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🎶 网易音乐" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider Ⓜ️ 微软服务" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🎥 奈飞节点" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 💬 OpenAi" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🇨🇳 台湾节点" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🎮 游戏平台" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🍃 应用净化" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🇺🇲 美国节点" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 📹 油管视频" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🎥 奈飞视频" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider Ⓜ️ 微软云盘" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🎯 全球直连" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🇸🇬 狮城节点" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🛑 广告拦截" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🌏 国内媒体" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🍎 苹果服务" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🚀 节点选择" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🚀 手动切换" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 📺 哔哩哔哩" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🌍 国外媒体" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 📢 谷歌FCM" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🇰🇷 韩国节点" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider default" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 📲 电报消息" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider Ⓜ️ 微软Bing" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🇭🇰 香港节点" 2024-11-21 20:29:53 level=info msg="Start initial Compatible provider 🇯🇵 日本节点" 2024-11-21 20:29:53 level=info msg="Start initial provider 人工智能通道" 2024-11-21 20:29:53 level=info msg="[TUN] Tun adapter listening at: utun([198.18.0.1/30],[]), mtu: 9000, auto route: false, auto redir: false, ip stack: System" 2024-11-21 20:29:53 level=info msg="Mixed(http+socks) proxy listening at: [::]:7893" 2024-11-21 20:29:53 level=info msg="TProxy server listening at: [::]:7895" 2024-11-21 20:29:53 level=info msg="Redirect proxy listening at: [::]:7892" 2024-11-21 20:29:53 level=info msg="SOCKS proxy listening at: [::]:7891" 2024-11-21 20:29:53 level=info msg="HTTP proxy listening at: [::]:7890" 2024-11-21 20:29:53 level=info msg="DNS server listening at: [::]:7874" 2024-11-21 20:29:53 level=info msg="Use tcp concurrent" 2024-11-21 20:29:53 level=info msg="Sniffer is loaded and working" 2024-11-21 20:29:53 level=info msg="RESTful API listening at: [::]:9090" 2024-11-21 20:29:53 level=info msg="Initial configuration complete, total time: 850ms" 2024-11-21 20:29:53 level=info msg="Finished initial GeoSite rule cn => dns.fake-ip-filter, records: 92599" 2024-11-21 20:29:52 level=info msg="Load GeoSite rule: cn" 2024-11-21 20:29:52 level=info msg="Geosite Matcher implementation: succinct" 2024-11-21 20:29:52 level=info msg="Geodata Loader mode: memconservative" 2024-11-21 20:29:52 level=info msg="Start initial configuration in progress" 2024-11-21 20:29:52 level=info msg="Initial configuration complete, total time: 939ms" 2024-11-21 20:29:52 level=info msg="Finished initial GeoSite rule cn => dns.fake-ip-filter, records: 92599" 2024-11-21 20:29:51 level=info msg="Load GeoSite rule: cn" 2024-11-21 20:29:51 level=info msg="Geosite Matcher implementation: succinct" 2024-11-21 20:29:51 level=info msg="Geodata Loader mode: memconservative" 2024-11-21 20:29:51 level=info msg="Start initial configuration in progress"
No response
不知道如何设置?
The text was updated successfully, but these errors were encountered:
发调试日志
Sorry, something went wrong.
我使用的是lede的固件,最新固件上tun模式没连接数,又编译了10月1号的lede的固件 tun模式正常了
也有人反映这个问题coolsnowwolf/lede#13100 (comment)
展开一下,也遇到有近似问题,openwet分支24.10,内核6.6.63, openclash是.54最近版本(.50到.54都测过),首先与ipv6的模式无关, opc自身不劫持dns(dns解析由前置mosdns完成解析和分流),
(1)当opc的 ipv4模式选择 tun 时,机场节点直连类型有ping值,而中转类型无ping值(不通); (2)当opc的ipv4模式选择 tun混合时,机场所有节点均有ping值(畅通)
当设置为(1)时,dns解析似乎有异常,比如 https://browserleaks.com/dns 就无法打开,github,chatgpt,微软store,windows设置中的时间手动同步,等都无法访问,而设置成(2)模式后均正常!
当设置成(2)时,目前仅发现移动端 perplexity 的app无法登陆账号。
No branches or pull requests
Verify Steps
OpenClash Version
v0.46.050 beta
Bug on Environment
Istoreos
OpenWrt Version
固件版本 iStoreOS 22.03.7 2024102509 内核版本 5.10.221
Bug on Platform
Linux-amd64(x86-64)
Describe the Bug
现在所有的调试方式都试了,现在的情况是有节点Ping,但是实际没有任何流量通过openclash。我测试了两个机场。之前上一个版本是正常的。我使用的是固件版本 iStoreOS 22.03.7 2024102509 内核版本 5.10.221 但是客户端clashx和安卓版的都可以用
To Reproduce
2024-11-21 20:29:56 OpenClash 启动成功,请等待服务器上线!
2024-11-21 20:29:56 第七步: 添加计划任务,启动进程守护程序...
2024-11-21 20:29:56 提示:开始添加自定义防火墙规则...
2024-11-21 20:29:56 提示:正在根据防火墙端口转发和防火墙通信规则添加端口绕过规则...
2024-11-21 20:29:55 提示:DNS 劫持模式为防火墙转发...
2024-11-21 20:29:55 第六步: 设置防火墙规则...
2024-11-21 20:29:52 第五步: 设置 Dnsmasq 程序...
2024-11-21 20:29:52 配置文件【/etc/openclash/白月光.yaml】测试成功...
2024-11-21 20:29:51 启动前调用内核测试配置文件...
2024-11-21 20:29:51 第四步: 启动主程序...
2024-11-21 20:29:51 提示:开始运行自定义覆写脚本...
2024-11-21 20:29:50 提示:为保证绕过 IP 正常工作,已在 Fake-IP-Filter 中添加规则【geosite:cn】...
2024-11-21 20:29:49 第三步: 修改配置文件...
2024-11-21 20:29:49 第二步: 组件运行前检查...
2024-11-21 20:29:48 第一步: 获取配置...
2024-11-21 20:29:48 OpenClash 开始启动...
2024-11-21 20:29:48 OpenClash 关闭成功!
2024-11-21 20:29:48 第六步:删除 OpenClash 残留文件...
2024-11-21 20:29:45 第五步: 重启 Dnsmasq 程序...
2024-11-21 20:29:45 第四步: 关闭 Clash 主程序...
2024-11-21 20:29:45 第三步: 关闭 OpenClash 守护程序...
2024-11-21 20:29:45 第二步: 删除 OpenClash 防火墙规则...
2024-11-21 20:29:45 第一步: 备份当前策略组状态...
2024-11-21 20:29:45 OpenClash 开始关闭...
2024-11-21 20:29:45 OpenClash 重新启动中...
OpenClash Log
OpenClash Config
No response
Expected Behavior
不知道如何设置?
Additional Context
No response
The text was updated successfully, but these errors were encountered: