A focused guide to the technical terms commonly found in v2rayNG and v2rayN configuration screens. Confirm each concept before changing protocol, subscription, traffic-routing or DNS settings, so similarly named options with different roles are not confused.
Start with “Protocols and Transport” when you see a name in a server configuration. For v2rayNG, v2rayN or core names, see “Cores and Clients.” Subscription updates, node lists and latency-testing terms are grouped under “Subscriptions and Nodes.”
When a connection is established but the result is unexpected, check “Routing and DNS” and “Android-Specific Settings” first. These definitions explain each parameter’s role; use the current server configuration as the authority for the actual values.
The protocol determines how the client and server organize communication data, while transport and security parameters define how the connection is established. Identical names do not mean parameters are interchangeable; preserve the complete original configuration when importing it.
A common client-to-server communication protocol in the Project V ecosystem. Configurations usually include a server address, port, user ID, encryption options and transport method, all of which must match the server. VMess is a protocol name, not a specific client or core.
A lightweight communication protocol commonly combined with TLS, REALITY, WebSocket or gRPC. VLESS itself is separate from transport security; when troubleshooting failures, check the user ID, flow control, transport type and security parameters independently.
A proxy protocol centered on password authentication and commonly used with TLS. The client must have the correct address, port, password and server name, with certificate options matching the server. Similar-looking Trojan configurations may still use different transport methods.
The transport method describes how protocol data is carried over a connection. Common options include TCP, WebSocket, HTTP/2 and gRPC. It is not a standalone node protocol and cannot be changed only on the client side. Path, Host and service name fields are also transport parameters.
The client handles the graphical interface and system integration, while the core handles protocols, routing, DNS and outbound connections. Distinguishing the two explains why the same core can appear in different clients.
One of the core implementations in the V2Ray ecosystem, responsible for parsing configuration and handling protocols, routing, DNS and connections. v2rayNG commonly uses the Xray core, although users interact with the client interface. Client and core versions may follow separate release schedules.
A community-maintained project continuing the Project V technical direction, with v2ray-core among its main components. V2Fly and Xray share technical roots, but their protocol capabilities, configuration fields and implementation details are not identical. Check the default core as well as the client when choosing an app.
A graphical client for Android with QR scanning, clipboard import, subscription updates, routing modes and per-app proxying. Connections typically use the system VPN interface to handle network requests from selected apps. Interface settings are ultimately converted into a configuration readable by the core.
A desktop client for Windows, macOS and Linux for managing servers, subscriptions, system proxy settings and routing rules. The desktop app provides the graphical controls, while the selected core handles the actual connection. System proxy behavior varies with each operating system’s network settings.
A subscription centrally updates configurations, while a node is an individual server entry that appears in the client after an update. Updating, filtering, selecting and latency testing are four separate actions and should not be treated as one step.
A centrally managed way for a server provider to publish configuration updates, usually as a subscription URL. After reading it, the client creates or updates the node list, but cannot fix permission, expiration or network problems with the URL itself. After changing the URL, run an update manually once.
An individual server configuration entry in a client, usually containing a protocol, address, port, authentication details and transport parameters. A node name is mainly for identification and says nothing about actual performance. Two nodes with the same displayed name may have different underlying configurations.
An organizational method for managing different subscription sources and their nodes separately. Groups can be updated independently and make it easier to filter servers by notes or conditions. If an update succeeds but the list is empty, check the current group and filters instead of repeatedly importing the URL.
The round-trip time measured while the client establishes a real connection and waits for the destination to respond. It is closer than a simple network probe to indicating whether the current configuration works. Results depend on the local network, test target, transport parameters and test time. Lower latency does not necessarily mean higher throughput.
Routing determines where requests go, while DNS converts domain names into reachable addresses. They affect each other: routing may rely on a domain or IP, and DNS results can change subsequent matches.
A matching rule that selects an outbound path based on the domain, IP address, port, network type or application conditions. Rules are usually evaluated in order, so the first match can determine the final path. Reconnect after making changes so the core loads the new configuration completely.
The process of sending different requests through direct, proxy or blocked outbound paths according to rules. Traffic routing is neither a protocol nor a single switch; it is a set of matching conditions and resulting actions. Before using a preset mode, understand the domain and IP ranges covered by its rules.
A data set organized by the region or network category associated with IP addresses, commonly used by routing rules for batch matching. GeoIP depends on the contents and update time of its data files; it is not a real-time geolocation service. Rules match resolved IPs, which may not correspond to the domain’s own category.
A rule data set organized by website domain categories, reducing the need to maintain domains individually. GeoSite and GeoIP match different targets: the former mainly handles domains, while the latter handles IPs. When custom rules overlap with built-in categories, also check the matching order.
A remote resolver configured in the client to convert domain names into the IP addresses required for connections. It may use regular DNS or an encrypted transport. After entering a remote DNS server, verify its actual path together with routing and local DNS settings.
Short for DNS over HTTPS, which carries DNS queries over HTTPS. Configuration usually requires a complete service URL rather than an IP address alone. DoH changes how queries are transported; traffic routing for each domain is still determined by the client’s DNS and routing rules.
Android clients typically use the system VPN interface to handle app traffic. Battery management, background restrictions and per-app scope all affect whether a connection stays active and which apps use the proxy.
A v2rayNG operating mode that uses the Android VPN interface to take over application network requests. The VPN interface is a system-provided traffic entry point; the client core still handles the actual protocol processing. Android allows only one active VPN connection of the same type at a time.
A feature for selecting which Android apps use the proxy. It can proxy only selected apps or exclude selected apps. Before enabling it, confirm which selection logic is active. After an app update or reinstall, check its package name and selection status again.
An operating mode that receives system traffic through a virtual network interface and passes it to the client core. It can cover more apps that do not actively read proxy settings, but it also requires coordination between DNS, routing and other network tools. If conflicts occur, first avoid enabling multiple traffic-capture methods at once.
A set of Android restrictions designed to control background battery use. If restrictions are too aggressive, the client may be suspended after the screen locks, causing connection drops or skipped background subscription updates. Decide whether to adjust them based on the device, battery needs and actual connection stability.
Security parameters are usually shared across the protocol, transport layer and certificate verification. When a connection fails, do not focus only on the “encryption” field; check the server name, public key, fingerprint and system time one by one.
A transport security solution in the Xray ecosystem. Its configuration often includes a public key, short ID, server name and client fingerprint. It is commonly combined with protocols such as VLESS rather than used as a standalone node protocol. Missing fields or extra spaces can prevent the handshake from completing.
A general security protocol for protecting transport connections. The client performs a handshake and certificate verification according to its configuration. The server name usually participates in certificate validation and should not be replaced with a node note. A significantly inaccurate system clock can also cause certificate validity checks to fail.
A set of implementation parameters describing TLS client-handshake characteristics, appearing as an optional or required field in some transport security configurations. It is not a hardware fingerprint and is not a user ID. Follow the server’s requirements and the support range of the current core when choosing a value.
A situation where DNS queries do not follow the intended resolver path, causing the query source to differ from the active proxy policy. Troubleshooting should cover system DNS, the client’s remote DNS, routing rules and TUN settings together. Changing only one DNS address usually does not prove that the query path has changed.
A configuration method in which the operating system provides a proxy address and port to desktop apps that follow system proxy settings. Unlike TUN mode, some apps may use their own network settings instead of reading the system proxy. Restore the system proxy before quitting the client to prevent a leftover port from blocking connections.
A mechanism that multiplexes multiple logical requests over one underlying connection, often shown in the client as “Enable Mux.” Its effect depends on the protocol, server support and workload; not every connection benefits from it. For compatibility problems, first restore the value recommended by the server.
For a first setup, follow Getting Started to import a subscription, choose a mode and check the connection. When you need to write traffic-routing rules, adjust DNS or manage multiple subscriptions, move on to Advanced Tips and work through the relevant sections.