Rule Provider Content
The content format of a file fetched by rule-providers depends on whether its behavior is set to classical, domain, or ipcidr — each uses a different format.
classical
Supports nearly every routing rule type (except RULE-SET/SUB-RULE), one per line, without the final outbound field:
google.yaml YAML
payload:
- DOMAIN-SUFFIX,google.com
- DOMAIN-KEYWORD,google
- DOMAIN,ad.com
- SRC-IP-CIDR,192.168.1.201/32
- IP-CIDR,127.0.0.0/8
- GEOIP,CN
- DST-PORT,80
- SRC-PORT,7777
domain
A list of domains, using Clash wildcard syntax for patterns (not the DOMAIN-WILDCARD syntax):
domain-list.yaml YAML
payload: - '.blogger.com' - '*.*.microsoft.com' - 'books.itunes.apple.com'
ipcidr
A list of IP ranges:
ip-list.yaml YAML
payload: - '192.168.1.0/24' - '10.0.0.0/8'
All three behaviors support both the yaml (with a payload: prefix) and text (plain text, one entry per line, no payload:) file formats, chosen via the format field. The actual rule content you write depends only on behavior, not on the format.