Proxy Groups proxy-groups
Proxy groups collect candidate proxies, built-in outbound options, or other groups under a name that rules can reference. select lets users choose manually; fallback prefers the first available option in the list. When a rule matches a group name, check which proxy the group currently selects to see where the connection actually goes.
Latency-Based Selection url-test
url-test probes candidate proxies using a specified URL and selects a route based on latency. interval sets how often to probe, while tolerance helps prevent frequent switching over small latency differences. This measures responsiveness to the test target; it does not guarantee that the selected proxy will be faster for other sites.
Rule-Based Routing
With mode: rule, the core checks connections against rules in order. Usually, the first matching rule determines what happens next. DOMAIN-SUFFIX can match a domain and its subdomains. If a subdomain needs different handling, put its more specific rule before the broader one.
GeoIP
GEOIP uses an IP dataset to match a destination address to a category, such as a country or region code. It does not match domain suffixes, and its result does not prove who operates a service. For a domain destination, a rule may need to resolve the address first; no-resolve prevents this rule from triggering a lookup just for the match.
Catch-All Rule MATCH
MATCH matches connections not handled by earlier rules. A common example is MATCH,DIRECT. It usually belongs at the end of the rule list; if placed earlier, later rules cannot handle connections it has already matched. If traffic unexpectedly hits the catch-all, check the preceding rules and the destination domain or IP in the logs.