Match criteria
Routing rules
Routing rules match connections against conditions such as destination domain, IP, or port, then send matching traffic to a specified outbound. In common V2Ray and Xray configurations, rules are checked in order, and matching stops at the first hit. If a broad rule comes first, exceptions below it may never take effect.
Outbound selection
Traffic routing
Traffic routing sends different traffic to different outbounds—for example, direct connections for LAN traffic and proxy connections for selected domains. It determines where connections go; DNS routing, by contrast, selects a resolver. When troubleshooting, check which resolver handles the domain and which routing rule the connection ultimately matches.
Rule data
GeoIP
In routing rules, GeoIP refers to tagged collections of IP ranges. Their exact contents depend on the data files loaded by the client. GeoIP matches IP addresses, not domain names, and cannot pinpoint a server's physical location. If a connection is identified only by domain, whether it can be matched by IP also depends on the routing DNS strategy.
Rule data
GeoSite
GeoSite rules reference tagged collections of domain names. The same tag may contain different entries in different data files. Matching uses the destination domain known to the client, not the location associated with the server's IP. If the client sees only an IP and cannot recover the domain, a domain-set rule will not match.