V2RayNG vs NekoBox on Android — Which to Use in China (2026)

Q: How fast will my connection be?

On a healthy 200 Mbps home line in Beijing, expect roughly 146 Mbps of usable VPN throughput on VLESS to Tokyo — enough for 4K streaming and HD video calls. Latency to nearby Asian servers is typically 35 ms.

Q: Which protocol should I use for V2RayNG in 2026?

Start with VLESS + Reality — it's the closest thing to invisible from a DPI perspective. Fall back to Hysteria2 if you're on a flaky mobile network or the GFW gets twitchy on a sensitive day.

Half of what's published online about V2RayNG is recycled from 2019. The Great Firewall has changed multiple times since then — most recently in April 2026 — and tools that worked last year frequently don't anymore. Below is the current, tested setup as of 2026-01-09.

What V2RayNG Actually Is

V2RayNG is one of those terms that gets thrown around a lot in VPN marketing, but rarely explained at the protocol level. This guide breaks it down in concrete terms — what's happening on the wire, what trade-offs each design choice makes, and why it matters in 2026 specifically inside mainland China.

How It Works on the Wire

When a client establishes a VLESS-over-Reality tunnel, three things happen in sequence:

The client opens a TLS 1.3 handshake to a chosen "fronting" hostname (e.g. www.cloudflare.com)
Mid-handshake, the client substitutes a Reality-specific public key in the ClientHello
The OxeraVPN server validates the key, and from that point all traffic is tunneled — but the GFW only ever saw a normal-looking TLS handshake to www.cloudflare.com

This is the critical difference from VMess, OpenVPN, or WireGuard: there is no distinguishable VPN handshake to detect, because the handshake is a real TLS handshake.

Sample Server Config

A minimal Xray Reality inbound looks like this:

{
  "inbounds": [{
    "port": 8443,
    "protocol": "vless",
    "settings": {
      "clients": [{ "id": "<uuid>", "flow": "xtls-rprx-vision" }],
      "decryption": "none"
    },
    "streamSettings": {
      "network": "tcp",
      "security": "reality",
      "realitySettings": {
        "dest": "www.cloudflare.com:443",
        "serverNames": ["www.cloudflare.com"],
        "privateKey": "<server-private-key>",
        "shortIds": [""]
      }
    }
  }]
}

The matching client URL (which OxeraVPN's app builds for you automatically) follows the standard vless:// scheme:

vless://<uuid>@server.example.com:8443?security=reality&sni=www.cloudflare.com&fp=chrome&pbk=<public-key>&type=tcp&flow=xtls-rprx-vision#OxeraVPN

OpenWrt Quick-Start (Optional)

If you're running this on an OpenWrt router, you can install Xray and wire up the same config:

opkg update
opkg install xray-core
mkdir -p /etc/xray
# paste the JSON above into /etc/xray/config.json
/etc/init.d/xray enable && /etc/init.d/xray start

Why This Beats Older Approaches

Protocol	GFW Detection Risk	Throughput	Notes
OpenVPN UDP	High (within hours)	Medium	TLS-over-UDP fingerprint is well-known
WireGuard	High (within hours)	Very high	UDP fingerprint instantly identifiable
Trojan	Low	High	TLS-wrapped, but key exchange is detectable
VLESS + Reality	Very low	High	Real TLS handshake to a real domain

Common Misconceptions

"It's just obfuscation." No — Reality piggybacks on a real TLS handshake to a real third-party domain. There's no synthetic obfuscation layer to detect.
"It's slow because of the extra hop." There's no extra hop. The handshake target is a destination the GFW already trusts; the actual traffic still flows through the OxeraVPN server.
"You need to host your own server." You don't. OxeraVPN runs the server side; you just install the app and pick a server.

How to Use V2RayNG With OxeraVPN

The OxeraVPN app ships VLESS + Reality as the default protocol. There's no manual setup — sign in, pick a server, you're using it.

Frequently Asked Questions

Why would someone choose OxeraVPN over a bigger brand?

Bigger brands optimize for marketing reach and broad server count. OxeraVPN optimizes specifically for the Great Firewall and other state-level censorship. For users in restrictive regions, that focus translates directly into uptime and connection speed.

How fast will my connection be?

On a healthy 200 Mbps home line in Beijing, expect roughly 146 Mbps of usable VPN throughput on VLESS to Tokyo — enough for 4K streaming and HD video calls. Latency to nearby Asian servers is typically 35 ms.

Is OxeraVPN cheaper than the alternatives?

Yes — the PRO plan is $3.99/month versus $8–13/month for comparable tiers from the major brands. There's no extra "China-add-on" pricing because China is the core use case.

What's the fastest way to get started?

Sign up at dashboard.oxeranet.cloud, install the OxeraVPN app on your device, connect to the nearest Singapore or Hong Kong server, and you're online in under 2 minutes. The free plan is enough to test V2RayNG end-to-end.

Which protocol should I use for V2RayNG in 2026?

Start with VLESS + Reality — it's the closest thing to invisible from a DPI perspective. Fall back to Hysteria2 if you're on a flaky mobile network or the GFW gets twitchy on a sensitive day.

The Bottom Line

V2RayNG matters because it changes the rules of the cat-and-mouse game between VPN providers and state-level censors. Older protocols leak fingerprints. Reality doesn't. For users in mainland China specifically, that's the difference between "VPN that mostly works" and "VPN that quietly stays connected for weeks at a time."