V2Ray TutorialDownload & Setup

Client Interfaces and Proxy Cores

Clients such as v2rayN handle subscriptions, configuration editing, and runtime controls; the selected core actually processes connections. V2Fly continues the Project V technology lineage, while Xray has developed independently from related foundations. When choosing a client, check the server’s protocol, transport, and security settings—not just the client name. For configurations involving REALITY or XTLS Vision, confirm that the selected core supports them. Before replacing a core, keep a copy of the existing configuration and test the new setup with a known-working connection.

{
  "log": {
    "loglevel": "warning"
  },
  "outbounds": [
    { "tag": "direct", "protocol": "freedom" }
  ]
}

Subscription URLs and Share Links

A subscription URL usually returns a set of connection profiles, while a share link describes a single connection. Don’t assume they’re interchangeable based on appearance alone. Before importing, verify the source and format. Create a separate subscription group in the client, update it, and check that the nodes appear. If the response is a webpage or login prompt, importing it repeatedly won’t fix a format mismatch. Subscriptions make it easier to update profiles in one place than to enter them individually, but later updates may overwrite local edits. Save important custom settings separately, and treat subscription URLs as sensitive information.

{
  "routing": {
    "rules": [
      {
        "type": "field",
        "domain": ["domain:example.com"],
        "outboundTag": "direct"
      }
    ]
  }
}

This is a standalone routing snippet, not a subscription file. Define an outbound with the same name before using it.

System Proxy and Routing Modes

The system proxy directs apps that honor system settings to a local listening port. Routing determines which outbound handles requests after they enter the core. These control separate stages—traffic entry and exit—and are not interchangeable. For an initial setup, start a working node, enable the system proxy, and test it in a browser. Some apps have their own proxy settings, which require the local address and port to be entered separately. A system proxy is easier to inspect and disable than capturing traffic through a network interface, but it doesn’t mean every app’s traffic is being routed through the client.

{
  "inbounds": [
    {
      "tag": "local-socks",
      "listen": "127.0.0.1",
      "port": 10808,
      "protocol": "socks",
      "settings": { "udp": true }
    }
  ]
}

Rule Order and Domain Resolution

Routing rules are matched in order, so specific conditions generally belong before broader ones. For direct connections to destinations in mainland China, first confirm that the direct outbound tag exists, then check domain rules, private-address rules, and the default outbound. Domain strategies are part of routing: they determine when domains are resolved for matching, and are not the same as DNS settings overall. Unlike sending all requests through one outbound, split routing requires maintaining rule data and match order. After making changes, test both the target domain and local network access rather than judging by a single webpage.

{
  "routing": {
    "domainStrategy": "IPIfNonMatch",
    "rules": [
      {
        "type": "field",
        "ip": ["geoip:private"],
        "outboundTag": "direct"
      },
      {
        "type": "field",
        "domain": ["geosite:cn"],
        "outboundTag": "direct"
      }
    ]
  }
}

Virtual Network Interfaces and Platform Differences

TUN routes traffic through a virtual network interface, making it useful for apps that don’t follow system proxy settings. It also involves permissions, routing, and DNS. Desktop and mobile clients implement TUN differently, so don’t assume every setting applies across platforms. Before enabling it, confirm that a standard proxy connection works, note your existing network settings, and check for other virtual networking tools. TUN affects more traffic than simply changing the system proxy. If the network goes down, first disable traffic capture and restore basic connectivity, then check permissions and interface conflicts one by one.

{
  "routing": {
    "domainStrategy": "AsIs",
    "rules": [
      {
        "type": "field",
        "ip": ["geoip:private"],
        "outboundTag": "direct"
      }
    ]
  }
}

This example shows only a private-address route, not a TUN interface configuration.