How Traffic Enters: App Proxy vs. Virtual Network Adapter

With a system proxy, the client writes a local proxy address to the operating system’s proxy settings. Apps such as browsers read those settings and send requests to Clash’s listening port. An app can also use its own proxy configuration; if it connects directly and no other mechanism intercepts the traffic, that connection won’t pass through Clash. Enabling the system proxy does not redirect every app’s network connections to the same port.

TUN creates a virtual network interface that sends IP packets on selected routes to the core. Apps connect as usual and don’t need to know the proxy address. For desktop clients using the mihomo core, the actual coverage depends on system routes, IPv4 and IPv6 settings, excluded networks, and whether another VPN handles the same destinations. “System-wide” means traffic is intercepted at the network layer; it does not mean every packet goes through a proxy node.

Desktop Traffic Entry Points Compared
ComparisonSystem proxyTUN
How traffic reaches the coreApps connect to a local proxy portThe system sends packets matching selected routes to a virtual interface
Typical coverageBrowsers and desktop apps that use the system settingsApps covered by the routes, including those that ignore the system proxy
UDPA standard HTTP system proxy does not capture arbitrary UDP datagramsCan receive UDP covered by the routes; forwarding it through a node also requires outbound UDP support
What to checkProxy address, port, app settings, and bypass listInterface, routes, permissions, DNS, and VPN conflicts

Traffic capture and routing are separate: TUN does not mean global proxy

System proxy and TUN determine how connections reach the core. Rules, global mode, and direct mode determine what the core does with them. For example, with TUN enabled in rule mode, a connection to a local service can match DIRECT and connect directly through the core, while a connection to another domain can match a proxy group. Both connections reach the core, but only the latter may exit through a proxy node.

Conversely, enabling only the system proxy and switching to global mode won’t make apps that ignore the system proxy automatically use Clash. To troubleshoot, first find the target traffic on the client’s Connections page, then check its matched rule and outbound route. A DIRECT entry usually means the connection reached the core but was routed directly. If there’s no entry, confirm the app opened a new connection; browser caching and connection reuse can make a single refresh hard to observe.

Permissions and Platform Differences: Understand What Each Switch Changes

Windows: User Proxy Settings and Service Mode

In Windows 11, go to Settings → Network & internet → Proxy to check the manual proxy address and port. If your configuration specifies mixed-port: 7890, the local proxy address using that port is typically 127.0.0.1:7890; clients may use a different port, so check the actual listening port. System proxy settings are usually applied for the current user. Background services and apps with separate network settings may not use the same proxy configuration.

Creating a TUN interface and changing routes may require administrator privileges. In the Windows version of Clash Verge Rev, check Service Mode and Virtual Network Mode in the System Settings area; labels and locations may vary by version. If the virtual network switch turns itself off immediately, check whether the service installed and started successfully, then review the core logs for interface or route errors. Changing nodes usually won’t fix a failure to create the interface.

macOS and Linux: Network Services and Desktop Environments Have Different Limits

On macOS, check proxy settings under System Settings → Network → select the current network service → Details → Proxies. After switching from Wi-Fi to Ethernet, check the active network service again. Linux has no single proxy setting that every desktop app follows: an app that supports GNOME proxy settings may use a different route from a terminal program that reads the HTTPS_PROXY environment variable. TUN requires a virtual interface and route configuration; on Linux, also check that /dev/net/tun is available and that the process managing network configuration has the required permissions, such as CAP_NET_ADMIN.

Don’t assume mobile clients use the same switch names as desktop apps. Android clients often use system VPN permission to create a virtual interface; per-app settings determine which apps are covered. A VPN-connected status only confirms that the tunnel is established. Check connection logs and routing rules to see how traffic actually exits.

Troubleshooting Compatibility: Narrow It Down by Checking Connections, DNS, and Routes

  1. Browser works, but terminal apps don’t: First check whether the terminal app has its own proxy options. If the local mixed port is 7890, use the command below to specify an HTTP proxy explicitly. If the command succeeds and a new connection appears in the client, that request reached the core through the local port. This doesn’t prove that the terminal app uses the system proxy by default or that TUN is working.
  2. Domains fail to load with TUN enabled: Check the logs to distinguish DNS resolution failures from outbound connection failures. mihomo’s dns-hijack can send matching DNS requests to its built-in DNS module, such as requests to port 53. Browser DNS over HTTPS is not handled as one of these requests. Compare the system DNS and the app’s secure DNS settings; don’t assume every domain failure is caused by the proxy node.
  3. Local network services become unreachable with TUN enabled: Check whether the destination still uses the original LAN interface. For example, in Windows PowerShell, run Find-NetRoute -RemoteIPAddress 192.168.1.20 to see which route is selected for that example address; replace it with the actual device address. If the connection reaches the core, check whether you need a direct rule. If the app relies on LAN broadcast or multicast discovery, check that traffic separately—a working unicast connection doesn’t mean device discovery is working.
  4. TCP works, but voice calls or games still have problems: First confirm whether the affected connection uses UDP. Then check whether it appears in the client logs and which rule it matches. TUN can receive UDP, but that doesn’t mean the selected node supports UDP forwarding. A web page loading or a successful node latency test doesn’t replace checking the traffic from the app itself.
curl --proxy http://127.0.0.1:7890 --head https://example.com/

If curl resolves to an alias in Windows PowerShell, use curl.exe to run the same command. If the local port refuses the connection, first check that the core is running and the port is correct. If the local port accepts the connection but the request times out, check the outbound route in the connection logs.

Which Should You Use? Start with the Narrowest Traffic Coverage

  • Mostly browsing in a web browser: Start with the system proxy. Confirm the target connection appears in the client logs, then make sure disabling the system proxy restores its previous state. If only one tool needs a proxy, you can configure that tool with the proxy address instead.
  • Several apps ignore the system proxy, or you need UDP traffic covered: Try TUN while keeping your existing rule mode. Test the target apps’ TCP, UDP, or DNS requests individually, then check that LAN services and IPv6 connections behave as expected.
  • You already use a corporate VPN or private network routes: Keep the existing network settings in place and confirm what changes are allowed. If both setups route the same subnet, note which route is selected before and after enabling TUN. Adjust automatic routing or excluded subnets only if you need broader traffic coverage.

After switching, test at least one destination that should use the proxy and one that should connect directly. Client connection logs show which rules and outbound routes were used. A public IP lookup only reflects the connection that made that request; it doesn’t prove other apps use the same node.