System Proxy vs. Global and Bypass China Modes: v2rayN Routing Guide

1. System Proxy and Routing Modes: Two Separate Settings

In v2rayN, selecting a server only chooses an available proxy outbound; it doesn't mean every app is using it. The usual path is: an app reads the proxy settings and sends a request to a local listening port, then the core selects a proxy, direct, or blocked route according to its rules. If any step fails, you may see a server respond to latency tests while webpages still won't load.

The desktop interface usually provides System Proxy and Routing options in the status bar, and the Windows tray menu may also include system proxy settings. Labels and locations can vary between builds, so look for what each setting does rather than a specific icon. Common Windows options include Set system proxy, Clear system proxy, and Do not change system proxy.

• Set system proxy: Writes the proxy settings to the operating system. Only apps that support these settings, such as browsers, will use the corresponding local proxy entry point.
• Clear system proxy: Removes the system proxy configuration. This doesn't shut down the core or stop apps from connecting through a port configured manually.
• Do not change system proxy: Leaves the current system settings as they are. A proxy configured earlier may still be active, so this option does not mean the proxy is off.
• Routing mode: Chooses an outbound route for requests that have reached the core. Switching to Global or Bypass China won't make an app that ignores the system proxy send traffic through the core.

2. Global, Bypass China, and Direct: Three Routing Strategies

Routing presets can be edited, and their behavior varies with the client build, core, and rule files. The comparisons below describe common strategies; presets with the same name aren't guaranteed to match rule for rule. If the results differ, inspect the selected rules and the outbound shown in the logs.

“China” in Bypass China refers to a rule category, not physical distance. Websites in mainland China that use overseas CDNs, and services with multiple regional endpoints, may match rules in unexpected ways. Rules are usually evaluated in order, so check the active core configuration for match conditions and the default outbound. A broad rule near the top can override more specific rules below it.

3. v2rayN Setup Order: Server, Port, System Proxy, Routing

For an initial test, use only the system proxy entry point, temporarily disable TUN, and turn off any separate proxy settings in browser extensions. This avoids stacking multiple entry points, which can make the browser's actual traffic path differ from what the status bar suggests. If you already have a working setup, note the original settings before making changes.

1. Confirm the active server. Select the server you want in the server list, then choose Set as active server from the right-click menu. Check the logs to confirm that the core starts successfully; a successful latency test doesn't guarantee webpages will load.
2. Check the local listening port. Go to Settings → Parameters and look for fields related to local listeners, SOCKS, or HTTP ports. Some interfaces use a single mixed port; refer to the actual configuration and startup logs.
3. Enable the system proxy. Under System Proxy, select Set system proxy. On Windows, check the address and port under Settings → Network & Internet → Proxy. On macOS, go to System Settings → Network → your current network service → Details → Proxies.
4. Test Global first. Under Routing, select the preset that uses Global routing. Open a known reachable HTTPS page and check the logs for the corresponding request. Don't change DNS, protocol, and transport settings at the same time.
5. Switch to everyday split routing. Select the Bypass China preset, then revisit services in mainland China and abroad. Start new connections during testing so the browser doesn't reuse existing connections and mask routing changes.

These two ports are examples, not promised defaults for the current version, and you don't necessarily need two separate listeners. If the startup log shows a single mixed port that supports both HTTP and SOCKS, use that port in both commands. Keep the address at 127.0.0.1 to limit testing to your computer; don't expose access to your local network just to troubleshoot a webpage.

# Run each command in a terminal with curl; on Windows, use curl.exe.
# First, replace the port with the value v2rayN is actually listening on.
curl --proxy http://127.0.0.1:10809 --connect-timeout 10 --head https://example.com/
curl --proxy socks5h://127.0.0.1:10808 --connect-timeout 10 --head https://example.com/

socks5h means the destination domain is resolved by the SOCKS proxy, rather than by the local machine before the request is sent. These commands specify the proxy entry point directly, so they don't depend on the system proxy setting. Use them to check whether the local entry point can handle requests. A successful result also confirms that the remote proxy path works only if the current routing mode selects the proxy outbound.

4. Everyday Split Routing and Temporary Troubleshooting: Two Setups

The recommendation to use Bypass China assumes that the client is receiving app traffic, the rule data is available, and the server connects successfully. If the entry point isn't working, changing the route won't fix how the app connects. Keep separate notes for everyday settings and troubleshooting to avoid forgetting to restore your setup afterward.

TUN is another way to capture traffic, not a “more complete Global routing mode.” It receives IP traffic that meets the capture conditions through a virtual network interface, then routing rules still determine the outbound. Enabling it may involve administrator privileges, system routes, DNS interception, and UDP support. Its coverage depends on the configuration and doesn't guarantee that all app traffic will be captured.

• Browser works, but other apps don't: Check whether the app follows the system proxy or has its own HTTP or SOCKS proxy settings.
• Local network printing or corporate intranet issues: Check whether local addresses and internal domains are being sent through the proxy outbound, and whether the intranet DNS server is reachable.
• If you need TUN: Note your system proxy, routing, and DNS settings first, then enable TUN on its own and test it. You don't need to enable the system proxy and TUN at the same time.

5. Switching Modes Has No Effect: Check the Entry Point and Outbound

When troubleshooting, check the log entry for a new request rather than relying only on the tray icon or connectivity test results. Seeing a destination in the log doesn't prove it used the remote server; check the outbound tag and connection errors too. Remove subscription URLs, credentials, and other sensitive settings before sharing logs.

6. Subscriptions, Protocols, and DNS: Separate Them from Proxy Modes

Subscriptions mainly provide server entries and related connection parameters. A successful subscription update doesn't mean the system proxy is enabled. Switching between VMess, VLESS, Trojan, or Shadowsocks servers won't fix routing rules either. These protocols describe how the proxy connection works, not which system traffic is captured.

• Server connection fails: Check the active server entry, server parameters, network reachability, and core errors first, without changing the routing mode.
• Destination lookup fails: Check whether the DNS server is reachable and where the domain is resolved—in the app, by the local core, or over the remote path. Direct routing doesn't necessarily mean DNS requests also go direct.
• Only certain sites have issues: Check rule order, domain lists, IP lists, and the default outbound. Don't assume the server is the cause of every problem.
• Different results on another device: The desktop system proxy settings in v2rayN don't apply directly to the Android VPN capture in v2rayNG or v2flyNG. Check the rules and DNS settings on each device separately.