Open
Description
Verify steps
- I have read the documentation and understand the meaning of all the configuration items I have written, rather than just piling up seemingly useful options or default values.
- I have carefully reviewed the documentation and have not resolved the issue.
- I have searched the Issue Tracker for the issue I want to raise and did not find it.
- I am a non-Chinese user.
- I have tested with the latest Alpha branch version, and the issue still persists.
- I have provided the server and client configuration files and processes that can reproduce the issue locally, rather than a sanitized complex client configuration file.
- I provided the simplest configuration that can be used to reproduce the errors in my report, rather than relying on remote servers or piling on a lot of unnecessary configurations for reproduction.
- I have provided complete logs, rather than just the parts I think are useful out of confidence in my own intelligence.
- I have directly reproduced the error using the Mihomo command-line program, rather than using other tools or scripts.
Operating System
Linux
System Version
DISTRIB_RELEASE='24.10.0'
Mihomo Version
alpha-g34de62d
Configuration File
NullDescription
using Remote rule providers,
when the yaml file with " - DOMAIN-SUFFIX," forget typing anything but leaving it blank. It will match all following commands !
check this Commit change. when this error ? happpen. as this rule-set match REJECT-DROP policy. whole traffic matched below this Rules will be matched!
IMO it should be report to upstream mihomo core as when I using it via OpenClash
Reproduction Steps
远程规则集中 如果只用 " - DOMAIN-SUFFIX," 未携带任何后缀. (是我忘记贴了!
并不会启动报错/检查语法规则.
当这个规则集在 Rule-Set 排序比较靠前时会 match 所有按顺序写入之后的规则.. 导致错误产生..
经检查不是下游 OpenClash 的问题.. 希望 mihomo 内核能够有检测/排除 " - DOMAIN-SUFFIX/REGEX," 为空集的 p0 事故?
Logs
OpenClash error logs:
> 2025-06-19 08:23:14 level=info msg="[TCP] 192.168.10.102:51247 --> 56.208.158.154:443 match RuleSet(Hijacking) using REJECT-DROP"
> 2025-06-19 08:23:14 level=info msg="[TCP] 192.168.10.102:51236 --> 149.154.167.41:5222 match RuleSet(Hijacking) using REJECT-DROP"
> 2025-06-19 08:23:14 level=info msg="[TCP] 192.168.10.102:51231 --> 91.108.56.135:443 match RuleSet(Hijacking) using REJECT-DROP"
> 2025-06-19 08:23:14 level=info msg="[TCP] 192.168.10.102:51239 --> 149.154.167.41:5222 match RuleSet(Hijacking) using REJECT-DROP"
> 2025-06-19 08:23:14 level=info msg="[TCP] 192.168.10.102:51248 --> 149.154.167.223:443 match RuleSet(Hijacking) using REJECT-DROP"
> 2025-06-19 08:23:14 level=info msg="[TCP] 192.168.10.102:51241 --> 149.154.167.223:5222 match RuleSet(Hijacking) using REJECT-DROP"
> 2025-06-19 08:23:14 level=info msg="[TCP] 192.168.10.102:51246 --> 95.161.76.100:5222 match RuleSet(Hijacking) using REJECT-DROP"
> 2025-06-19 08:23:14 level=info msg="[TCP] 192.168.10.102:51230 --> 91.108.56.135:5222 match RuleSet(Hijacking) using REJECT-DROP"
> 2025-06-19 08:23:14 level=info msg="[TCP] 192.168.10.102:51237 --> 149.154.167.223:443 match RuleSet(Hijacking) using REJECT-DROP"
> 2025-06-19 08:23:14 level=info msg="[TCP] 192.168.10.102:51242 --> 149.154.167.50:5222 match RuleSet(Hijacking) using REJECT-DROP"
> 2025-06-19 08:23:11 level=info msg="[TCP] 192.168.10.102:51228 --> 149.154.167.223:443 match RuleSet(Hijacking) using REJECT-DROP"
> 2025-06-19 08:23:06 level=info msg="[TCP] 192.168.10.102:51227 --> 91.108.56.135:443 match RuleSet(Hijacking) using REJECT-DROP"
> 2025-06-19 08:23:06 level=info msg="[TCP] 192.168.10.102:51226 --> 91.108.56.135:443 match RuleSet(Hijacking) using REJECT-DROP"
> 2025-06-19 08:23:05 level=info msg="[TCP] 192.168.10.102:51225 --> 149.154.167.223:443 match RuleSet(Hijacking) using REJECT-DROP"
> 2025-06-19 08:22:59 level=info msg="[TCP] 192.168.10.102:51224 --> 149.154.167.223:443 match RuleSet(Hijacking) using REJECT-DROP"