forked from MetaCubeX/ClashMetaForAndroid
-
Notifications
You must be signed in to change notification settings - Fork 4
Routing and Rules
Nemu-x edited this page Jul 7, 2026
·
2 revisions
In Rule mode, ClashFest decides per-connection whether traffic goes through the proxy, direct, or is rejected — based on the rules in your config. The Routing tab lets you view and customise them.
For each connection the engine walks the rule list top-to-bottom and applies the first match. A rule matches on things like:
-
Domain —
DOMAIN,DOMAIN-SUFFIX,DOMAIN-KEYWORD -
IP —
IP-CIDR,GEOIP(country) -
Rule sets / providers — big managed lists (
RULE-SET,geosite,mrs) - Process / app, port, network (tcp/udp)
Each rule points at a policy: a proxy group, DIRECT, or REJECT.
Open Routing to see:
- Rules — the effective ordered list, with source badges (which came from your subscription vs. added manually).
- Rule providers — the managed rule sets your config references, with on/off toggles.
-
Geo databases — GeoIP / Geosite data used by
GEOIP/geositerules, with a manual update action.
- Manual rules you add are combined into the same ordered list and can be reordered, edited, or removed.
- Subscription rules are toggle-only (on/off) — you don't edit them, because they get refreshed by the subscription. Disabling one survives subscription updates.
- Changes are staged and applied with Save (with a dry-run preview).
Advanced rule types (logical
AND/OR/NOT, process, port, protocol) are supported. Per-rule custom DNS is intentionally not offered — it's non-standard for Mihomo rules.
- Profiles & Nodes — Rule vs Global mode
- Settings — DNS & Hosts, per-app proxy
📱 User Guide
- Getting Started
- Profiles & Nodes
- Routing & Rules
- Settings
- Deep Links
- Encrypted Subscriptions
- Troubleshooting
🏢 Operator API
📺 Companion