Why start with v2rayNG
v2rayNG is useful for the first proof because it removes router complexity. Import the VLESS share link, select the profile, test on mobile data, test on Wi-Fi, and verify the exit IP. If the endpoint fails on Android, moving it to OpenWRT will not fix it.
Android validation checklist
- Import a fresh private share link.
- Confirm the client uses a current Xray core.
- Check Reality fields: serverName, public key, short ID, flow, and port.
- Test Wi-Fi and mobile data separately.
- Verify exit IP and DNS path before changing any fields.
When to move to OpenWRT
Move to OpenWRT only after the endpoint works on one device. Router setup adds more layers: xray-core package, config file syntax, local SOCKS or transparent inbound, DNS forwarding, firewall marks, and per-device policy routing. Test each layer separately.
OpenWRT failure points
On older routers, CPU can limit VLESS Reality performance. On mixed IPv4/IPv6 networks, traffic can skip the rules you expected. DNS can leak if dnsmasq or the local resolver is not routed through the proxy. Transparent routing can fail if firewall marks are incomplete or if only TCP is covered while UDP leaks.
If you need a private endpoint
A managed endpoint is most useful after you know the client and router are configured correctly but public endpoints stay unstable. Proxy Poland provides private VLESS/Xray access on real mobile infrastructure, plus HTTP, SOCKS5, and OpenVPN for simpler clients.
