V2Ray / Glossary

V2Ray Glossary

Import configurations, capture traffic, and route connections. Browse by category and identify which step each setting controls.

Protocol fields / transport fields / security fields

Protocols & Transport

VMess

VMess is a proxy protocol in the Project V ecosystem. The user ID in a configuration must match the server settings; transport is configured separately. Seeing VMess tells you the protocol type, but not whether it uses WebSocket or has TLS configured.

VLESS

VLESS separates identity from transport security and does not encrypt payloads itself. To protect the connection between client and server, check the configured security layer, such as TLS or REALITY. Two nodes using the same protocol may still have different security settings.

Trojan

Trojan is a proxy protocol that typically runs over TLS and uses a password for authentication. TLS verification and protocol authentication are separate steps: the former verifies the server, while the latter determines whether the server accepts the client's credentials. When troubleshooting a connection, don't confuse these two types of errors in the logs.

REALITY

REALITY is a transport security mechanism supported by Xray and often paired with VLESS. VLESS identifies the proxy protocol, while REALITY identifies the connection's security mechanism, so both can appear in one configuration. Availability depends on the core integrated into the client and its feature support.

Transport

Transport describes how proxy data is carried between the two ends, for example over WebSocket or gRPC. The same proxy protocol can use different transports, and using the same transport does not mean the path or service name is the same. When comparing node settings, check the transport and security layer separately.

Project / core / interface

Cores & Ecosystem

Project V

Project V is the open-source networking project ecosystem that includes V2Ray; it is not the name of a graphical client. Documentation about V2Ray core configuration usually covers protocols, inbounds, outbounds, and routing. Menu labels are up to each client and may not match core fields exactly.

V2Fly

V2Fly is a community project continuing development of the V2Ray core, and v2flyNG uses its core. A client being able to read a sharing format does not mean the core supports every field in that configuration. To compare compatibility, check the core actually integrated and its version, not just whether the import succeeded.

Xray

Xray is a core project that branched from the V2Ray ecosystem, and v2rayNG uses Xray. Some configuration structures are similar between the two cores, but not every transport, security, or flow-control field is interchangeable. Before migrating, confirm that the target core supports the fields in question, then distinguish a configuration parsing error from a connection failure.

Graphical client

A graphical client imports configurations, switches nodes, and manages connections; the core typically handles protocol processing and routing. The same core may appear under different menu options in different clients, and some fields may not be shown in the interface. When consulting a guide, first check whether it describes where to find a button or how the underlying feature works.

Configuration source / active connection / test results

Clients & Subscriptions

Subscription

A subscription uses a URL to fetch and refresh a set of configurations. A successful update only means the client retrieved content it could process; it doesn't mean every node in the list can connect or that the selected node is now active. Subscription URLs may contain access credentials, so hide the full URL in screenshots and logs.

Subscription group

A subscription group is a local way for a client to organize configurations by source, making nodes easier to find and refresh. Two sources may offer nodes with the same label; groups help show where they came from. Switching list groups does not change the active connection or automatically modify routing rules.

Node

A node is a configuration entry in the client that points to a connection endpoint, usually with an address, port, protocol, and connection settings. The name in the list is just a label; two entries with the same name may point to different endpoints. When troubleshooting, check the actual configuration rather than relying on the label.

Real connection latency

Real connection latency is typically measured by sending a request through the selected node to a specified address and recording how long it takes. Unlike a test that only checks whether a port accepts a connection, its exact timing depends on the client implementation. For useful comparisons, keep the test address and network conditions the same; low latency does not mean high throughput.

System proxy

A system proxy is a proxy setting provided by a desktop operating system. An app sends relevant requests to the proxy only if it reads and follows that setting; apps with their own network settings may take another route. Seeing system proxy enabled in the client does not mean every app's connections are going through the core.

Match conditions / DNS resolution path / outbound selection

Routing & DNS

Routing rule

A routing rule links match conditions, such as a domain, IP, or port, to a target outbound. Rules are checked in order, so if a broad rule matches first, later rules won't process the same connection. If a rule appears not to work, check both its order and the destination information the core actually received.

Traffic routing

Traffic routing sends different connections through direct, proxy, or block outbounds. It determines the path a connection takes; it does not split a download across multiple nodes. If an app's traffic is not captured by the system proxy or a virtual interface, it won't enter the core's routing process.

GeoIP

GeoIP provides IP address range classifications for routing, often used to identify private addresses or group public ranges by region. Rules check whether the destination address falls within a dataset. A matching regional label does not identify the user's location or show that the service operator is in that region.

GeoSite

GeoSite provides domain collections organized by labels for use in routing rules. Which labels exist and which domains they contain depend on the data file actually loaded by the client. If the core only sees the destination IP and has not obtained the domain, it cannot match that IP directly against a domain collection.

FakeDNS

FakeDNS assigns a synthetic address during DNS resolution and stores the mapping between that address and the original domain. When an app connects to the address, the core can recover the domain after capturing the connection and continue routing. The synthetic address is not the actual service address; connections may fail if they take a path that cannot access the mapping.

DNS leak

A DNS leak occurs when queries are sent to a resolver outside the intended path. Before deciding whether one occurred, establish which resolver should handle each domain and which outbound the queries should use. Even if a web request takes the expected route, that alone does not show how its DNS query was routed.

Domain strategy

The domain strategy in routing determines whether to resolve a domain so IP rules can be tried. For example, IPIfNonMatch checks the available destination information first; if nothing matches, it resolves the domain and tries the IP conditions. If the same field name appears in an outbound or DNS module, interpret it in the context of that configuration layer.

System permissions / traffic capture / background operation

Android Networking

VpnService

VpnService is the VPN service interface provided by Android. After the user approves the system VPN connection request, the client can create a virtual network interface to receive traffic within its scope. The VPN indicator means the interface is established, but does not by itself prove that the selected node works.

TUN mode

TUN mode receives IP packets through a virtual network interface, so apps don't have to read the system proxy settings. Which traffic enters the interface still depends on routing and the capture scope. A desktop client's TUN toggle and Android's VPN permission are different entry points, though both involve a virtual network interface.

Per-app proxy

Per-app proxy settings determine which apps send traffic through the current VPN on Android. In bypass mode, apps on the list stay outside the VPN; with an allowlist, only apps on the list use it. This layer determines whether traffic enters the client; the core's routing rules choose the outbound afterward.

Doze

Doze is Android's power-saving feature that limits some background activity when a device has been idle for an extended period; it does not necessarily start as soon as the screen locks. Disconnections after screen lock may also be caused by manufacturer-specific background restrictions or network changes. Check when the disconnection occurred and review the client logs before deciding whether to adjust battery optimization settings.

For step-by-step help with the actual menus, see the connection and verification guide, or read the advanced routing and DNS configuration guide.