Routing
To understand a rule, first find its matching conditions, then see which outbound handles matching traffic.
Routing rule
Routing rules match traffic using conditions such as domain, destination IP, and port, then send matching traffic to a specified outbound. V2Ray-family cores generally check rules in order, so an earlier, broader rule may match first and prevent a later exception from taking effect. When troubleshooting, find the rule that actually matched, then check whether it selected the right outbound.
GeoIP
In routing configurations, GeoIP usually refers to a set of IP address ranges organized by region or purpose, used to match destination IPs. It does not match domains directly. Whether a rule matches an IP resolved from a domain also depends on the routing domain strategy. If the same site gets inconsistent matches, check whether it resolved to different IPs.
GeoSite
In routing configurations, GeoSite usually refers to collections of domain rules organized by category, such as geosite:category-ads-all. A collection provides matching criteria; it does not decide whether traffic goes direct, through a proxy, or gets blocked. If a category is missing or results differ from expectations, first check that the local data file includes it, then review rule order.
Routing
Routing sends different connections entering the client to different outbounds—for example, sending local network services direct while proxying other matching traffic. Routing happens after traffic reaches the client. If an app neither uses the system proxy nor has its traffic captured by TUN, changing routing rules alone won’t affect it.