Configuration and Networking Terms

Clash Glossary

From subscriptions to outbound connections: understand proxy protocols, configuration fields, and routing rules, plus the roles of DNS, TUN, and mihomo in the connection flow.

Proxy Protocols

A protocol defines how a client communicates with a server; a node stores the specific settings needed to establish a connection.

Proxy Node
A proxy node is a single proxy outbound the core can connect to, usually defined by its protocol, server address, port, and authentication settings. Its name is just a reference in the configuration; any region or route label in the name plays no part in the handshake. If a node fails to connect, distinguish between an unreachable address, mismatched settings, and an incorrect outbound selection.
Shadowsocks(SS)
Shadowsocks is an encrypted proxy protocol, usually specified in configuration as type: ss. Even with the correct address and port, a connection will fail if the encryption method or password differs between the two sides. If the server uses an additional transport plugin, the client must support it and use matching plugin settings.
VMess
VMess is a proxy protocol whose nodes typically use a uuid to identify the user. If the connection uses a transport such as WebSocket, options like the hostname and path must match the server. If authentication fails, check the credentials and make sure the device clock is accurate.
VLESS
VLESS and VMess can both use a uuid to identify users, but they are not compatible protocols. You cannot convert a node by changing only its type. VLESS does not provide encryption by itself; connection security comes from accompanying settings such as TLS or REALITY. When importing a node, check that the core supports both the protocol and its transport options.
Trojan
Trojan typically connects over TLS and uses a password for protocol-level authentication. Server authentication and the node password are separate: the former involves the certificate and expected server name, while the latter is checked by the server. If the logs show a certificate error, changing the node password will not fix it.

Configuration Fields

First identify where the configuration comes from, then see which fields define the local ports, node lists, and policy groups.

Subscription
A subscription is usually a URL for fetching a remote configuration or node list; the server determines the response format. Clients may refresh subscriptions on a schedule, so edits to a downloaded file can be overwritten at the next update. Subscription URLs may contain credentials, so redact the full link before sharing screenshots or logs.
YAML
YAML uses space-based indentation to represent structure, mappings for key-value pairs, and lists for entries such as rules or nodes. Incorrect indentation can make a file unreadable or place a field at the wrong level. A file that a YAML parser can read is not necessarily supported by the current core in every field.
Mixed Proxy Port (mixed-port)
mixed-port lets the core accept both HTTP proxy and SOCKS5 connections on the same local port. Apps still need to be configured with a proxy type they support; this is not the server port of a remote node. If the logs report that the address is already in use, choose another listening port and update the app or system proxy settings to match.
Proxy Providers (proxy-providers)
proxy-providers declares a source of nodes, loaded from a remote URL or local file, so you do not have to put every node in the main configuration. Policy groups use use to reference a provider by its key, not by a node name. A full client subscription and a node collection loadable by the core do not necessarily use the same file structure.

Routing Rules

Rules decide which outbound a connection uses; policy groups decide which member is currently selected.

Rule-Based Routing
With mode: rule, the core checks connections against the entries in rules in order. The first matching rule determines the outbound. The core does not automatically prefer rules that seem more specific, so a broad condition placed first can prevent later exceptions from matching. To trace a connection, first find the rule it actually matched, then check where that rule points.
Policy Groups
A policy group is a named collection of outbounds that can include nodes, other policy groups, or built-in outbounds such as DIRECT. Select groups let users choose a member, while test-based groups choose one based on probe results and configuration settings. Matching a group only means that traffic was passed to it; the actual connection depends on the group's current selection.
GeoIP
GeoIP matches a destination IP address against IP range data. GEOIP,CN,DIRECT is a common rule format. GeoIP does not identify a website's language or operator, and the same domain may match different rules depending on its resolved address. To route by domain rather than IP range, use an appropriate domain rule.
Rule Providers (rule-providers)
Rule providers store reusable domain, address, or other matching conditions separately. rule-providers declares their source and behavior type. The main configuration references a provider with RULE-SET and specifies an outbound in that rule. A loaded rule provider does not take part in matching unless it is referenced in rules.
MATCH
MATCH matches every connection not handled by earlier rules and usually belongs at the end of the rule list. MATCH,DIRECT sends the remaining traffic directly; you can also target a defined policy group. If MATCH comes earlier, none of the entries after it will get a chance to match.

DNS & Networking

Resolving domains, capturing traffic, and establishing connections are separate steps. Success at one step does not mean the others are working as intended.

DNS
DNS looks up records such as the IP addresses associated with domain names. When the core receives a DNS query, it can choose an upstream resolver based on its configuration; apps may also make queries through their own resolution mechanisms. A successful lookup only means an address was returned—it does not show that the destination port is reachable or that the connection went through a proxy.
Fake-IP
Fake-IP is a DNS enhancement mode. The core assigns a temporary address to a domain, then uses the mapping to recover the domain when a connection to that address arrives, allowing rules to match by domain. For apps that depend on real DNS results or for local network domains, use fake-ip-filter to add exceptions as needed.
DNS Leaks
A DNS leak occurs when queries bypass the intended resolution path and go to a resolver that was not meant to be used. A website opening through a proxy does not mean the browser's DNS queries all use the same outbound. Compare the resolver actually used with the expected configuration; deliberately configured direct DNS is not a leak.
TUN Mode
TUN mode uses a virtual network interface and system routes to pass matching IP traffic to the core. It can handle apps that do not read system proxy settings. The traffic captured depends on routes, permissions, and exclusions; once traffic reaches the core, its outbound is still determined by the configuration. Enabling TUN does not mean every connection will be forwarded through a proxy node.
Node Latency Testing
In a Clash client, latency usually means the time taken to probe a specified test address through an outbound, not the link's maximum throughput. Two probes are meaningfully comparable only when their targets, network conditions, and test methods are similar. A single timeout may also mean the test address is unreachable, so check it separately from the destinations you actually use.

Clients & Cores

The interface manages configuration and displays status; the core reads the active configuration and handles actual connections.

Clash Client
A Clash client usually refers to an app with a graphical interface for importing subscriptions, switching policies, managing the system proxy, and viewing logs. Different apps can use the same core, but their interface options, override mechanisms, and update methods may differ. When switching clients, check whether local settings need to be configured again.
mihomo
mihomo is a proxy core descended from Clash.Meta. It parses configuration, applies rules, and establishes outbound connections. The core version in the logs and the client version shown in the interface use separate numbering schemes. When troubleshooting compatibility with a configuration field or protocol, first confirm which core and version are actually running.
System Proxy
The system proxy is an operating system setting that apps can read, usually pointing to the client's local listening address and port. Only apps that follow this setting will hand connections to the proxy; some use their own options or connect directly. If the system proxy remains enabled after the client closes, apps may keep trying to reach a port that is no longer listening.