Clash / mihomo · Glossary

Clash Glossary

Look up terms from the client interface or YAML fields. If routing results differ from what you expect, first check whether the traffic was captured, which rule matched, and which proxy the selected group ultimately chose.

Browse configuration fields and YAML examples · See installation and import steps

Core and Protocols

mihomo

mihomo is the proxy core that parses configuration, matches rules, and establishes outbound connections. The client interface imports files and changes settings; the core is what actually applies them. If a field is not recognized, check the version of the core that is running—not just the app version.

Proxy

A proxy is an endpoint defined in the configuration, typically with a protocol, server address, port, and protocol-specific parameters. Nodes can be listed directly under proxies, while proxy groups choose among candidate endpoints. A display name can be used as a reference, but it does not tell you whether a proxy is reachable or which protocol it uses.

Proxy Protocol

A proxy protocol defines how the client and server exchange data. The node's type determines how its other fields are interpreted, so switching protocols requires a complete set of parameters supported by the server—not just a name change. The protocol used by a local app to connect to the proxy may also differ from the one the core uses to connect to a remote node.

Latency

The milliseconds shown in a dashboard usually come from a probe to a specific URL; they are not round-trip times to every destination. Different test URLs, timeout settings, and connection reuse can make readings hard to compare. Test download speed and sustained stability separately. A single timed-out probe does not mean every connection will fail.

Configuration Structure

Subscription

A subscription is a source of configuration that a client periodically retrieves, usually from a URL. The response may contain a complete configuration or just a list of proxies; whether it can be enabled directly depends on the response format and client support. Subscription URLs may contain credentials, so do not share the full link when troubleshooting import issues.

YAML

YAML uses indentation to represent hierarchy and organizes data into key-value pairs and sequences. For example, an indented enable: under dns: belongs to the DNS configuration; it is not a top-level switch. Use spaces for indentation. After validating the syntax, check that field names, nesting, and value types meet the core's requirements.

Proxy Providers proxy-providers

proxy-providers organizes proxies by provider, which can point to a remote URL or a local file. Proxy groups reference providers with use, so you usually do not need to rewrite each group's candidate list when the provider updates. If the provider updates successfully but the group remains empty, check the reference name and filter conditions.

Override

Overrides keep local changes separate from the original subscription, such as adjusting DNS fields or inserting an exception before subscription rules. Replacing a field with the same name, appending to a list, and prepending to a list are different operations; their exact behavior depends on the client. After updating a subscription, review the merged configuration to make sure your changes are still at the intended level and in the right order.

Proxy Groups and Rules

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.

DNS and Network Stack

Fake-IP

dns.enhanced-mode: fake-ip makes the core return synthetic addresses for eligible DNS requests and store the mapping between each domain and address. The core can use that mapping to recover the domain when it handles a subsequent connection. If a LAN service or app requires real addresses, exclude it with fake-ip-filter as needed.

DNS Leak

A DNS leak occurs when DNS queries take an unintended resolution path—for example, web traffic goes through a proxy while queries are still handled by the local network's resolver. Whether this counts as a leak depends on the expected resolution path, not the country or region shown by a test page. To troubleshoot, check the browser's secure DNS, the system resolver, and the upstream DNS servers used by the core separately.

TUN Mode

tun.enable: true enables TUN through the configuration, capturing traffic via a virtual network interface and routing. It can cover apps that ignore system proxy settings, but coverage is limited by system permissions, routing rules, and exclusions. After enabling it, verify separately that the intended traffic and DNS queries are handled as expected.

Mixed Port mixed-port

mixed-port accepts HTTP and SOCKS proxy requests on a single listening port. 7890 is a common example, not a default for every client; apps should use the port that is actually listening. For connections from other devices, also check allow-lan, the listen address, and firewall settings.

Clients and Platforms

Graphical Client GUI

A graphical client provides an interface for importing configurations, selecting policies, and viewing logs. It may bundle the core or manage a separate core process. Even clients using similar cores can differ in override syntax, menu layout, and system integration. When choosing a client, first confirm platform support, then compare the features you actually need.

System Proxy

System proxy settings provide an address and port for apps that follow them; they do not install routes to capture traffic. Apps that ignore the system proxy may connect directly or use a separately configured in-app proxy. If the client is closed while the system still points to a local port that is no longer listening, apps following that setting may lose network access.

Processor Architecture

x64, amd64, and x86_64 usually refer to the same 64-bit x86 architecture; arm64 and aarch64 usually refer to 64-bit ARM. Before downloading, check the operating system, architecture, and package format. If a client offers multiple builds, choose the native build for your system.