System Proxy, Global Mode, and Bypass Mainland China Explained

First, separate system proxying from routing modes

“System proxy” and “Global Mode” are not the same switch. System proxying is the operating system’s connection entry point. When v2rayN enables it, the client writes a local proxy address to Windows network settings. Browsers and other applications that follow system proxy settings read this address and send requests to v2rayN’s local listening port.

Global Mode and Bypass Mainland China are core-level routing modes. After a request reaches the Xray or V2Fly core, routing rules decide whether to use a remote node, connect directly, or block the request. Switching to Global Mode alone does not capture every connection on the system if application traffic never enters the local proxy.

Think of the complete path as “application → system proxy or manual proxy → local port → core routing → remote node or direct exit.” The first half determines whether traffic reaches the client; the second determines how it is forwarded afterward.

Which apps can system proxying capture?

v2rayN’s “Auto-configure system proxy” changes the current user’s Windows proxy settings. Common browsers usually follow this setting, and some download tools, desktop apps, and updaters do too. When disabling it, use “Clear system proxy” so Windows returns to a direct configuration.

System proxying is not network-layer forwarding. Command-line tools may read only their own settings or environment variables, while games often create TCP or UDP connections directly. Some apps also provide separate proxy options. Even when running alongside a browser, these connections may bypass the system proxy completely.

In v2rayN 7.x, the local SOCKS port commonly starts at 10808, and the HTTP port at 10809. Confirm the actual ports under “Settings” → “Parameter settings” → “Basic settings”. If the ports were changed, update any manually configured proxy addresses in other applications as well.

How common apps are affected

• Browsers: They usually read the Windows system proxy, so enabling it sends HTTP and HTTPS requests to v2rayN.
• Command-line tools: They may require a separate HTTP, HTTPS, or SOCKS proxy. Do not rely only on the system proxy status shown in the taskbar.
• Download tools: Check the app’s own “Connection” or “Proxy server” settings; some tools use direct connections by default.
• Games and real-time communications: They commonly use UDP or manage connections independently. System proxying usually cannot capture them completely, so evaluate the app’s own support or TUN mode.
• Local network apps: When accessing routers, print services, or file shares, direct connections are usually preferable. Avoid sending private-network addresses through a remote node.

How Global Mode and Bypass Mainland China forward traffic

Global Mode generally means that every connection already inside the core, unless excluded by a higher-priority rule, is sent through the current remote node. It is useful for confirming that a node works and for temporary tasks with hard-to-classify destinations, but websites in mainland China, software updates, and large downloads may also take the remote route.

Bypass Mainland China splits traffic using domain groups, IP databases, and private-network rules. Mainland China domains and IPs usually connect directly, while other destinations use the proxy; local network addresses should generally remain direct as well. The goal is to avoid unnecessary remote traffic while preserving proxy access to other destinations.

Routing does not look only at the domain shown in the browser. A page may request its main domain, image domains, API domains, and content delivery addresses at the same time. If the rule data is outdated or DNS results do not align with routing decisions, the page may load while images or sign-in APIs fail.

In a single comparison test on a 300 Mbps home connection, a direct download from a mainland China content delivery node reached about 286 Mbps, Bypass Mainland China reached about 281 Mbps, and Global Mode through a rate-limited node reached about 84 Mbps. These figures show only that route selection affects performance; other connections may differ substantially.

v2rayN settings paths and verification steps

Before configuring anything, select a working server and confirm that the client core has started. A latency value in the node list does not guarantee that real requests will succeed; latency tests only show that one type of probe received a response. Verify actual behavior with browser requests, connection logs, and the destination itself.

Interface labels in v2rayN 7.x may change between minor releases, but the roles remain the same: the system proxy entry controls Windows proxy status, the routing entry controls predefined split-routing rules, and parameter settings control basics such as local listening ports.

1. Select the target node in the server list, set it as the active server, and confirm that the status bar shows no core startup errors.
2. Open “Settings” → “Parameter settings” → “Basic settings” and note the local SOCKS and HTTP listening ports. Common values are 10808 and 10809.
3. From the “System proxy” menu, choose “Auto-configure system proxy” so apps that follow Windows settings connect to the local HTTP proxy.
4. Under “Routing” → “Predefined rules”, select “Bypass Mainland China” for everyday split routing. Temporarily switch to “Global” when troubleshooting rule issues.
5. Reopen the browser page you want to test so old connections, connection pools, or DNS caches do not continue using the previous route.
6. Check the client log for the destination domain, destination IP, outbound tag, and error details to confirm whether the request used the proxy or a direct connection.

Does the application use the system proxy?
├─ No: set 127.0.0.1:10808 for the application, or evaluate TUN
└─ Yes: check whether the request reaches the local listening port
   ├─ Not reached: check the port, listening status, and system proxy address
   └─ Reached: check the routing match and node connection result
      ├─ Global works, Bypass Mainland China fails: check rule data and DNS
      └─ Both modes fail: check the node, protocol configuration, and core logs

Choosing a mode for browsing, downloads, and gaming

Everyday browsing usually needs both fast access to mainland China services and reachability for other destinations. System proxying combined with Bypass Mainland China provides a more stable default: mainland requests connect directly, other requests follow the rules to the current node, and browsers can usually read the Windows proxy configuration.

For large downloads, first identify the source. Mainland China mirrors, cloud drives, and content delivery nodes are better accessed directly to avoid using remote bandwidth. If the server is elsewhere and direct access is unstable, temporarily use Global Mode or add a proxy rule for the specific domain.

You cannot determine whether a game is covered just because “system proxy enabled” is shown. Many games use UDP, separate launchers, or their own networking components and do not read system proxy settings. Global Mode still handles only connections that have entered the core; it cannot automatically send uncaptured traffic through the proxy.

Choose the mode based on the destination

• Many mainland China websites and local network resources: prefer Bypass Mainland China and retain direct rules for private addresses.
• Need to quickly verify that the node itself works: switch briefly to Global Mode, then restore the everyday rules after testing.
• A single domain takes the wrong path under Bypass Mainland China: add an explicit domain rule instead of keeping Global Mode enabled permanently.
• The app provides a SOCKS proxy option: enter 127.0.0.1 and the actual SOCKS port, then confirm how DNS is handled.
• The app completely ignores proxy settings: evaluate v2rayN TUN mode and check administrator permissions, routing conflicts, and DNS configuration.

Common problems and what to check

Choosing the wrong mode usually produces a suboptimal route, while a port or node error causes the connection to fail outright. During troubleshooting, record the mode before and after switching, destination domain, time, and log error. Avoid changing the node, routing, DNS, and port at once, or you will not know which change mattered.

If only some resources fail, check the other domains referenced by the page rather than only the main domain in the address bar. If mainland China services slow down in Global Mode, that is a common result of route detours; switch back to Bypass Mainland China or add a direct rule.

A simplified conclusion for choosing a mode

System proxying answers “which apps enter v2rayN”, while Global Mode and Bypass Mainland China answer “which exit they use afterward”. These settings can be combined but cannot replace each other. Once this distinction is clear, most cases of “Global Mode is enabled but has no effect” or “the browser works but the game does not” can be troubleshot layer by layer.

For ordinary desktop use, start with Auto-configure system proxy together with Bypass Mainland China. Switch briefly to Global Mode when checking a node or routing issue. For apps that ignore system proxy settings, check manual proxy support or TUN instead of repeatedly changing the split-routing preset.

• Everyday default: enable the system proxy and choose Bypass Mainland China for routing.
• Rule troubleshooting: switch temporarily to Global Mode and compare the result for the same destination.
• Mainland China downloads: prefer direct connections and confirm that the download tool is not forcing a local proxy.
• Gaming connections: confirm how traffic is captured before discussing Global Mode or split routing.
• Local network access: keep private addresses direct to avoid affecting routers and local devices.