Repository navigation
EN Auto Routing
The Auto Routing feature in FlowWeaver is designed to ensure most websites can be connected without manual configuration. When a requested domain does not match any defined rule, the AutoRouter automatically determines the processing logic based on the current configuration.
Important
Priority Note: Subscription rules and rules manually defined in the "Rules Panel" have the highest priority (when a subscription is active, its rules load and the built-in rules are hidden). The Auto Routing (AutoRouter) only intervenes when the requested domain does not match any existing rules.
Recommended for most users — currently the only supported auto-routing mode:
-
Workflow:
- Listen for the requested domain.
- Rule Matching: Check if the domain matches any subscription rule or user-defined site rule. If it matches, execute according to the rule and end the routing logic.
- GFWList Query: If no rules match, query the built-in local GFWList.
- If not in list: Connect directly (Direct).
-
If in list:
- Detect if the target is a Cloudflare node (queries IP via DoH and compares with CIDR).
-
If Cloudflare: Apply
MITM + ECH Injectionmode; use Cloudflare optimized IP. -
If not Cloudflare: Apply
TLS-RF(TLS Fragmentation) mode; use upstream DoH to query IP.
Auto Routing relies on the local GFWList database (local cache file only, no network updates).
The software automatically identifies domains belonging to the Cloudflare infrastructure and prioritizes applying ECH injection strategies.
In the "Connection Logs," requests processed by Auto Routing are tagged as AutoRouted, making it easy to trace routing strategies.
If auto-routing fails, you can manually configure a specific rule for that domain.
When a subscription is active, its routing rules take priority; domains not covered by the subscription rules still go through the auto-routing flow above.