How to Choose Between System Proxy, Global, and Bypass Mainland China: V2Ray Proxy Modes Explained

Understand the Two Switches First: the System Proxy Controls the Entry Point, Routing Mode Controls the Exit

“System proxy” and “global mode” are not options at the same level. The system proxy determines whether an app’s traffic enters v2rayN; global and bypass-mainland routing determine whether traffic that reaches the V2Ray or Xray core uses a proxy outbound or a direct outbound. Treat them as two decisions made in sequence, and many seemingly contradictory behaviors become easy to explain.

After you enable v2rayN’s automatic system proxy on Windows, the client points the operating system’s HTTP and HTTPS proxy settings to a local listening port. In a typical setup, the local address is 127.0.0.1 and the mixed proxy port is 10808. Browsers and other programs that follow system proxy settings send requests to this entry point, after which the core applies the routing rules.

Not every program reads the system proxy. Some download tools, game launchers, and command-line programs use their own network settings; some accept only an HTTP proxy, while others let you enter a SOCKS address separately. If the browser works but a particular app still connects directly, first check whether that app uses the system proxy instead of immediately changing nodes.

Traffic Differences Between Global and Bypass Mainland China

Global mode generally means that every connection already inside the core is sent through the current proxy outbound. “Global” does not mean that every network connection on the computer is automatically intercepted; programs that do not read the system proxy or point to the local port manually may still access the network directly.

Bypass mainland China uses rule-based split tunneling. The core chooses an outbound based on the domain, destination IP, LAN address, and rule sets. A common setup sends private addresses, mainland China domains, and mainland China IPs directly, while using the proxy for everything else. Local services, websites in mainland China, and common download sources can then be accessed without sending data through a remote node first.

Routing decisions do not simply inspect the last few characters of a URL. Domain requests can match domain categories, and the resolved connection may then be evaluated against the destination IP; LAN addresses such as 192.168.1.1 and 10.0.0.1 should normally stay direct. If custom rules appear before the default rules, they can change the final result, so review both the rule contents and their order when adjusting routing.

Choosing a Mode for Browsing, Downloads, and Multiple Apps

For most everyday use, start with “automatically configure the system proxy + bypass mainland China.” Browsers and desktop apps that follow system proxy settings will enter the local port automatically, while mainland China services and LAN destinations connect directly according to the rules. Compared with using global mode all the time, this combination usually reduces unnecessary remote relays and is less likely to interfere with access to local devices.

Before downloading large files, check whether the download program reads the system proxy. If the download address is already reachable directly, bypass-mainland mode is usually the better choice. If the program has its own proxy settings, choose HTTP or SOCKS and enter the local address and port currently shown by the client. Do not judge proxy use by download speed alone; check the client’s connection logs to confirm the destination and outbound.

When several apps run at once, use the principle of “split by default, handle exceptions separately.” Let browsers and office software use the system proxy; specify the local port inside tools that require a fixed proxy; and leave apps that do not need a proxy on a direct connection. This is more stable than repeatedly switching to global mode and helps prevent one high-volume task from consuming all available node bandwidth.

Three Practical Examples

1. Browsing the web in a browser only: enable automatic system proxy configuration and use bypass-mainland routing. Browsers usually follow the system settings directly, so no additional extension is required.
2. The browser works, but a command-line program does not: check whether the program reads HTTP_PROXY, HTTPS_PROXY, or SOCKS settings. If needed, configure it separately in the current terminal session instead of switching the entire client to global mode.
3. A destination fails in split-tunneling mode: switch to global mode temporarily and test again. If it immediately works, the node is probably usable; the issue is more likely the domain category, destination IP decision, or custom rule order.

Set Up and Verify Traffic Paths in v2rayN

Menu labels may vary slightly between v2rayN versions, but the setup sequence is largely the same. Select an available node on the main screen first, then check the local listening port. The usual path is “Settings” → “Parameters” → “Basic Settings”; confirm the local mixed port. If the page shows a value other than 10808, use the client’s actual value for any later manual configuration.

Next, use the v2rayN menu in the taskbar notification area to configure the system proxy. For everyday use, choose “Automatically configure system proxy”; when pausing it temporarily, choose “Clear system proxy.” “Do not change system proxy” only means that the client will not modify the operating system settings; it does not mean that the core has stopped. Apps with a local port configured manually may continue connecting.

Switch routing modes from the routing option on the main screen; detailed rules are usually managed under “Settings” → “Routing Settings.” Beginners should start with the standard split-tunneling rules supplied with the client. Before adding custom rules, note the original mode and rule order, change one condition at a time, and test before making further adjustments.

1. Select a node on the v2rayN main screen and start the core, making sure the status bar shows no port-conflict warning.
2. Open “Settings” → “Parameters” → “Basic Settings” and note the local listening address and mixed port, for example 127.0.0.1:10808.
3. Set the system proxy to automatic configuration and set the routing mode to bypass mainland China.
4. Visit a LAN address, a website in mainland China, and a destination that requires a proxy separately, then check whether all three request types behave as expected.
5. Open the connection log and verify the destination domain, destination port, and matched outbound. An outbound such as direct means the request did not pass through a remote node; a proxy outbound name means the request was sent through the current node.

Application request
  → System proxy or in-app proxy
  → 127.0.0.1:10808
  → V2Ray/Xray routing decision
  ├─ direct: local direct connection
  └─ proxy: current VMess or VLESS node

Keep the destination, node, and network environment unchanged during testing, and switch only one option. For example, the same webpage failing in bypass-mainland mode but working in global mode provides useful routing evidence. If you also change nodes, modify DNS, and restart the network, it becomes difficult to tell which step caused the change.

Use Timing Differences as Supporting Evidence

Timing is only supporting evidence. In one sample test, a LAN administration page took about 2 to 8 ms over a direct connection but could time out entirely through an unsuitable proxy path. A static resource in mainland China might load directly within 20 to 60 ms, yet take more than 150 ms through a remote node. Values vary by location, network, and node; the connection log’s routing result remains authoritative.

Common Questions and Fixes

Proxy mode issues often appear as “some apps work while others do not” or “switching to global fixes it.” These symptoms usually involve both the entry point and routing layers. Checking them in a fixed order is faster than repeatedly updating the subscription.

The short version is: use automatic system proxy configuration with bypass-mainland routing for everyday use, enter the local port separately for apps that ignore the system proxy, and reserve global mode for temporary verification or tasks that genuinely need one unified proxy exit. After every change, check the connection log to confirm the actual path instead of relying only on the connected status shown in the interface.