v2rayN Guide · Term Reference

V2Ray Glossary

When you encounter an unfamiliar field while editing a node, updating a subscription, or configuring routing, first identify which connection layer it belongs to, then decide which setting to change.

Protocols & Transports

Protocols define how proxy requests are formatted; transports define how the data is carried.

Proxy protocols

VMess

VMess is a proxy protocol in the Project V ecosystem. It uses a user identifier for authentication and defines the message format for proxy requests. When configuring a connection, check the transport and security layer as well as the protocol. Two VMess configurations are not interchangeable just because they use the same protocol.

Proxy protocols

VLESS

VLESS is a proxy protocol that commonly identifies users with a UUID. The protocol itself does not provide encryption; whether a connection is encrypted depends on the selected security layer, such as TLS or REALITY. The VLESS label alone does not tell you how secure a connection is.

Proxy protocols

Trojan

Trojan is a proxy protocol that uses a password for authentication and is typically used over TLS. The proxy password and server certificate serve different purposes: the server uses the password to authenticate the client, while the client uses the certificate to verify the server.

Transport

WebSocket

WebSocket is a bidirectional transport that can carry proxy traffic. It is a transport setting, not an alternative to VMess or VLESS. The path configured at each end must match. TLS is a separate setting and cannot be inferred from the WebSocket name.

Cores & Clients

The client provides the settings interface; the core reads the configuration and handles connections.

Proxy core

Xray

Xray is a proxy core that handles connections, runs protocols, and applies routing rules—not a graphical interface for users. When a desktop client asks you to choose a core type, you are choosing which core will interpret the configuration. Settings with the same name may behave differently across cores.

Community project

V2Fly

V2Fly is an open-source community project that continues the Project V ecosystem and maintains the V2Ray core. When troubleshooting compatibility, distinguish the community project from the core actually running and the GUI client version. A client interface update does not necessarily change core behavior.

Desktop client

v2rayN

v2rayN is a desktop GUI client that brings node management, subscription updates, core startup, and system proxy settings together in one interface. A node appearing in the list only means its configuration has been saved; it does not mean the core connected successfully or that the current app is using the proxy.

Mobile client

v2rayNG

v2rayNG is an Android GUI client that uses the Xray core to handle proxy connections. In proxy mode, it typically routes traffic through Android's VPN interface. Check permissions and per-app proxy settings on the device rather than looking for the desktop system proxy menu.

Subscriptions & Nodes

First, distinguish the URL used to update a set of configurations from the link used to import a single node.

Subscription updates

Subscription URL

A subscription URL is the address a client uses to retrieve a set of node configurations. It is usually entered under “URL” in the subscription group settings. Saving a group and updating a subscription are separate actions: saving stores the address; updating fetches and parses its contents. Do not share URLs containing access credentials publicly.

Connection configuration

Node

A node is a connection configuration in the client list, typically containing a server address, port, protocol, and authentication settings. Its remarks are just a display name, and identical names can refer to different configurations. When troubleshooting, compare the configuration fields, not just the names.

Connectivity testing

Proxy latency

Proxy latency usually measures how long the client takes to reach a test address through a node. It is not the same as measuring a TCP handshake directly to the server. Results vary with the test address, local network, and node status; low latency does not mean high download bandwidth.

Routing & Traffic Rules

First make sure traffic enters the core, then check which rule it matches.

Matching conditions

Routing rule

Routing rules direct connections that have entered the core to an outbound based on conditions such as domain, destination address, or port. Rule order and the handling of unmatched traffic both affect the outcome. When checking routing, first confirm which rule set is actually enabled.

Outbound selection

Traffic routing

Traffic routing lets rules determine whether each connection goes direct, through a proxy, or is blocked. Setting a domain to direct only affects connections that match that rule. Images, APIs, and other domains on the same page may each match different rules.

IP range data

GeoIP

In routing, GeoIP usually refers to IP range data grouped by geographic region or another category, used to match destination IPs. It does not measure a server's physical location in real time. Matching depends on whether the core has the IP address and whether the data file covers that range.

Domain rule data

GeoSite

GeoSite is categorized domain rule data that a core can reference to match domains. Unlike GeoIP, which matches IP ranges, GeoSite matches domains. Category names do not guarantee fixed contents; check the data version in use to determine what it covers.

App proxy entry point

System proxy

A system proxy is an operating system setting that provides proxy access to apps. “Set system proxy” configures that access for apps that honor the setting. It does not determine which outbound handles traffic after it enters the core. If an app ignores the system proxy, changing routing alone will not send its connections through the core.

DNS & Networking

Consider the traffic entry point, domain lookups, and lookup results separately.

Domain lookup

DNS resolution

DNS resolution looks up domain records and is commonly used to find the IP address for a website. Apps, the operating system, and the proxy core may all make DNS requests. When troubleshooting, distinguish the address a domain resolves to from the route a connection takes afterward.

Virtual interface

TUN mode

TUN mode uses a virtual network interface to capture IP traffic selected by system routing, without requiring every app to read the system proxy setting. Which traffic enters the interface depends on routing, exclusions, and the client implementation. Enabling TUN does not automatically send all traffic through a proxy outbound.

Domain mapping

FakeDNS

FakeDNS returns temporary mapped addresses to traffic-handling paths that support it and keeps track of each address's original domain. The core can use this mapping to identify the destination domain and apply domain rules. These temporary addresses are not the destination server's actual addresses.

DNS query path

DNS leak

A DNS leak occurs when domain lookups use an unintended resolver or network path, exposing the requested domains to another party. A website loading successfully does not mean DNS followed the expected path. Also check whether the browser uses its own Secure DNS and whether any direct-connection exceptions are configured.

Encryption & Security

Whether a connection is encrypted and whether the other party's identity has been verified are two separate questions.

Connection security layer

TLS

TLS encrypts connections and protects their integrity, and typically uses certificates to verify the server's identity. In a proxy client, TLS for the node connection and HTTPS for the website are separate layers. Checking one does not replace checking the other.

Connection security mechanism

REALITY

REALITY is a TLS-handshake-based connection security mechanism supported by Xray and commonly used with VLESS. VLESS describes the proxy layer; REALITY describes the connection's security layer. The client and server need compatible implementations and settings.

Handshake field

SNI

SNI (Server Name Indication) is a field in the TLS handshake that tells the other end which hostname the client wants to connect to. When multiple hosts share an IP address, the server can use SNI to select the right configuration and certificate. SNI is handshake data; it does not prove the other party's identity.

Peer identity

Certificate validation

Certificate validation checks whether the TLS peer presents a certificate with the expected name, a valid date range, and a trusted chain. If validation fails, first check the system clock, target hostname, and certificate chain. Skipping validation will not fix these issues and removes protection against server impersonation.