Configuration reference · 20 terms

V2Ray glossary

When you see options such as “System Proxy,” “Enable TUN,” or “Real Connection Latency” in v2rayN, use the categories below to find what they mean. Each card explains which settings layer a term belongs to and how it differs from similar options.

Protocols & Transport

Protocol

VMess

VMess is a proxy protocol in the Project V ecosystem that authenticates with a user ID. After importing a profile, make sure the protocol, user ID, and transport settings match the server. If the connection fails, check which setting is mismatched rather than just whether the server address is reachable.

Protocol

VLESS

VLESS is a lightweight proxy protocol that can be paired with security mechanisms such as TLS or REALITY. A VLESS node tells you the proxy protocol, but not which transport or security mechanism it uses. When comparing configurations, check the protocol, transport, and transport security separately.

Protocol

Trojan

Trojan is a proxy protocol that typically runs over TLS and uses a password for authentication. Along with the credentials, the client’s TLS settings must match the server. A certificate name mismatch and an incorrect password occur at different stages and should be diagnosed separately.

Transport security

REALITY

REALITY is a transport security mechanism provided by Xray for VLESS connections. In the node editor, VLESS refers to the proxy protocol, while REALITY refers to transport security; they are not two options in the same dropdown. Before switching cores, confirm that the target core supports the required mechanism.

Cores & Ecosystem

Proxy core

Xray

Xray is a proxy core that emerged from the V2Ray ecosystem. It handles connections, routing, and related DNS settings. v2rayN and v2rayNG provide graphical interfaces; the core applies the configuration after you select a server or change settings. A field appearing in the interface does not guarantee support in the active core.

Community project

V2Fly

V2Fly is an open-source community project that continues development of the V2Ray core and related components. v2flyNG uses the V2Fly core, so it differs from v2rayNG, which uses Xray, in more than just the app name. Before migrating a server configuration, check that its protocol, transport, and fields are compatible.

Subscriptions & Nodes

Configuration source

Subscription

A subscription fetches and updates multiple server configurations from one source. Adding a subscription URL, fetching the server list, and selecting the active node are separate actions; a successful update does not switch the active connection. Subscription URLs may contain access credentials, so hide the full URL in screenshots you share.

Server entry

Node

A node is a connection profile in the server list, usually containing an address, port, protocol, and authentication details. Two nodes can use the same address but different ports or transports, so the number of entries does not equal the number of servers. A remark helps identify an entry but is not used for authentication.

List management

Subscription group

Subscription groups organize server entries into separate lists by source or purpose, making them easier to browse and update. Switching groups in the interface usually only changes which entries are visible; it does not make a category of apps use that group. To change the connection, select a server. To route traffic by destination, edit the routing rules.

Routing & Traffic Routing

Matching criteria

Routing rule

A routing rule combines matching criteria with an outbound selection. It can match details such as a domain, destination IP, or port. In Xray, rules are checked in order, and the first match determines the outbound for that connection. A broad rule placed before a specific exception may prevent the exception from taking effect.

Outbound selection

Traffic routing

Traffic routing uses rules to send different connections to different outbounds, such as sending some directly and others through a proxy. It only applies to traffic handled by the client. If an app bypasses the system proxy, the client may never receive its connections, so routing rules cannot be applied.

IP address collection

GeoIP

GeoIP is categorized IP address data used for routing matches. Categories can represent regions or ranges such as private addresses. The actual classifications depend on the data file in use; an IP category does not prove a server’s physical location. Whether a domain request matches an IP rule also depends on whether routing has access to its resolved address.

Domain collection

GeoSite

GeoSite groups domains by category so a routing rule can reference an entire set. Categories and their members depend on the data file in use, and updates can change which domains match. If the client only has the destination IP and not the domain, it cannot match that connection directly against a domain collection.

DNS & Network Modes

Domain name resolution

DNS

DNS looks up addresses and other records associated with domain names. The operating system, browser, and proxy core may each use different resolvers, so changing DNS in the client may not affect every app. To troubleshoot, first identify which component is making the query, then check its resolver and network path.

Virtual network interface

TUN mode

TUN mode receives IP traffic routed by the operating system through a virtual network interface, without requiring every app to read the system proxy settings. Which traffic enters the interface still depends on system routes, exclusions, and platform permissions. If local network access stops working after enabling TUN, check whether the relevant subnet is included in the routing scope.

Address mapping

FakeDNS

FakeDNS assigns a temporary mapped address to a domain. When an app connects to that address, a client or core with access to the mapping record can restore the original domain and then apply domain rules. This is not the destination server’s actual address; if the connection does not return to the component that created the mapping, it may fail.

Query path

DNS leak

A DNS leak occurs when a query takes a resolution path outside the intended policy—for example, when a query meant for a specified resolver is handled by the system default instead. Some apps have built-in DNS resolution, so their query paths may differ even when web requests use a proxy. Compare observed behavior with the intended policy rather than judging by the resolver’s name alone.

Client Settings

How apps connect

System proxy

The system proxy is a proxy setting provided by the operating system to apps. Typically, only apps that honor the setting will use it. v2rayN’s “Set system proxy” option writes the corresponding settings; “Clear system proxy” removes them. Clearing this setting is separate from turning off TUN.

Connection testing

Real connection latency

Real connection latency is the time recorded when accessing a test destination through the selected node. It is not the round-trip time from pinging the server address. Test procedures can vary between versions, and results depend on the destination and current network conditions. For a fair comparison, use the same test method and destination; a single result cannot predict download speed.

outboundTag

Outbound tag

An outbound tag is the name used to identify an outbound in a configuration. In Xray, the outboundTag in a routing rule references the target outbound’s tag. The tag name does not determine behavior: even if it is named direct, check whether the outbound it refers to is configured for a direct connection.