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.060-beta
Immortalwrt
ImmortalWrt 23.05.4 r28061-399f9a1db3
Linux-amd64(x86-64)
以下是添加的规则:
上面的规则只要去掉no-resolve就不会报错,分流也正常。
另外,其他通用规则中增加no-resolve并不会报错。
只要在AND/NOT/OR等规则中添加no-resolve就能复现。
以下是openclash启动时的内核报错信息: 2024-11-18 20:16:50 level=error msg="rules[46] [AND,((RULE-SET,Force_Reject),(SRC-IP-CIDR,192.168.0.200/32)),REJECT,no-resolve] error: proxy [no-resolve] not found"
No response
希望能增加no-resolve的支持。
The text was updated successfully, but these errors were encountered:
需要去内核那边提
Sorry, something went wrong.
No branches or pull requests
Verify Steps
OpenClash Version
v0.46.060-beta
Bug on Environment
Immortalwrt
OpenWrt Version
ImmortalWrt 23.05.4 r28061-399f9a1db3
Bug on Platform
Linux-amd64(x86-64)
Describe the Bug
以下是添加的规则:
上面的规则只要去掉no-resolve就不会报错,分流也正常。
另外,其他通用规则中增加no-resolve并不会报错。
To Reproduce
只要在AND/NOT/OR等规则中添加no-resolve就能复现。
OpenClash Log
OpenClash Config
No response
Expected Behavior
希望能增加no-resolve的支持。
Additional Context
No response
The text was updated successfully, but these errors were encountered: