Beginner-friendly reference
Use this glossary when tutorials mention a term that is not a button in your current client.
Terms
| Term | Meaning |
|---|---|
| Core | The program that performs proxy connections, rule matching, DNS and TUN behavior, such as Clash, Mihomo, sing-box or Xray-core. |
| Client | A GUI or app that manages subscriptions, switches, logs and settings, such as Clash Verge Rev, FlClash or Stash. |
| Subscription URL | A remote profile URL provided by a service vendor. The client fetches nodes, groups and rules from it. |
| Profile | An imported configuration containing sections such as proxies, proxy-groups, rules and dns. |
| Proxy / Node | A remote outbound entry such as SS, VMess, VLESS, Trojan or Hysteria2. |
| Proxy Group | A group that organizes nodes as select, url-test, fallback, load-balance and similar policies. |
| Rule | A routing condition based on domain, IP, process, port, region or other matchers. |
| DIRECT | Direct outbound without a remote proxy. |
| REJECT | Reject or block the matched request. |
| DNS | The resolver module that affects domain rules, Fake-IP and routing decisions. |
| Fake-IP | A virtual IP assigned to domains so transparent proxy traffic can still be mapped back to domain rules. |
| TUN | A virtual network interface mode that captures more app traffic and usually needs OS permissions. |
| Mixed Port | A local port that accepts both HTTP and SOCKS proxy traffic. |
| External Controller | A RESTful API endpoint used by GUIs and dashboards to inspect and control runtime state. |
| Provider | A remote proxy list or rule list that can update independently. |
| GEOSITE / GEOIP | Domain-set or IP-geo data used by routing rules. |
| SNI | The server name in TLS handshakes, important for TLS, Reality, Trojan and VLESS nodes. |
| ALPN | TLS protocol negotiation such as h2 or http/1.1. |
| Reality | A transport and disguise capability commonly used with Xray/VLESS; support depends on the core. |
| UDP / QUIC | Required by Hysteria2, TUIC, some games and DNS scenarios. |
| Rule Mode | Rule-based routing, the recommended default for most users. |
| Global Mode | Routes everything through one proxy policy, useful for short tests. |
| Direct Mode | Routes everything directly, useful for isolating proxy-related support checks. |
| Logs | The key evidence for import status messages, DNS, certificate support checks, occupied ports and timeouts. |
How to Use It
- If a term names a protocol, check the protocol center.
- If a term names a core or client, check the core center and client status page.
- If a term names a YAML field, compare it with the configuration examples before editing.