Node HandbookNODE HANDBOOK中文
Clash Verge Rev · TUN

TUN mode connects but there is no internet in Clash Verge Rev

If the system proxy also fails, TUN is not your first problem. This page only applies once the proxy path is known to work and enabling TUN alone breaks connectivity — and it is built around one-node, one-rule comparisons.

Node Handbook editorial team ·

Material checked on 2026-11-14. Error strings are quoted verbatim so you can match them against your own log.

First decide whether this is really a TUN problem

  • Disable TUN, keeping the current subscription, mode and node.
  • Enable the system proxy and open an ordinary HTTPS site.
  • Confirm a connection appears in the client's connection list, then compare the exit IP with an IP check page.

If the system proxy also fails, work on the subscription, nodes, core or system proxy first. Only when the system proxy is fine and enabling TUN alone kills connectivity does the rest of this page apply. The official quick start also treats the system proxy and TUN as two different capture methods: the system proxy mainly covers programs that honour system settings, while TUN captures games, command-line tools and other software that never reads the system proxy.

Scope: Clash Verge Rev desktop on Windows, macOS and Linux. Interface labels can change between versions. This page is a reproducible diagnostic order, not a claim to cover every system, antivirus product or corporate network policy.

Build a three-state baseline on one node and one rule set

To avoid changing node, mode and the TUN switch at the same time, first record the OS version plus the Clash Verge Rev and Mihomo versions, then pin one node and one rule mode. Use a plain website that your network normally reaches as the direct baseline, and pick a separate HTTPS target you expect to reach through the proxy. Change only the capture method at each step.

StateWhat to recordHow to read the result
System proxy off, TUN offA site you know is reachable directly, plus system network and DNS stateIf a single site fails, try another known-reachable target before declaring a base-network fault
Same node, system proxy on, TUN offProxy test page, client connection list, exit IPA failure here points at the subscription, node, core or system proxy
System proxy off, TUN onlyKeep node, rules and target unchanged; check that the test application has no separate proxy setting, then check the virtual interface, connection list, page load and DNS resultOnly a matching connection entry after the system proxy is off justifies looking further into TUN capture; if only this step fails, check the service, routes and DNS capture

Keep the timestamp of each step together with the redacted log lines. If the service install already reported an error, move to service install failed; if the system proxy itself is broken, move to system proxy has no internet. Neither situation should be treated with TUN settings first.

Step 1 — service mode and permissions

TUN has to create a virtual adapter and adjust system routes, which needs more privilege than an ordinary system proxy. Confirm in the settings that service mode is available before enabling TUN. After installing or updating the service, restart the client, and do not run an old Clash build, another VPN or a second Mihomo frontend at the same time.

  • Windows: confirm the service install reported no error and that Windows Security or a third-party firewall is not blocking the Mihomo core.
  • macOS: check the system network and firewall settings; if the log clearly reports a permission denial, follow the operating system's own prompts and record the result before and after any change.
  • Linux: check whether the current service log reports a TUN device or route write failure; permission configuration differs by distribution and should follow that system's documentation.

Do not rely permanently on "start as administrator every time" to paper over a failed service install. Permission only allows TUN to be established; it does not make nodes, DNS and routes correct.

Step 2 — did the virtual adapter actually appear?

After enabling TUN, look at the system adapter list: an interface created by Mihomo or Clash should normally be present. If the switch flips straight back, the log reports a creation failure, or no new interface appears at all, keep checking the service, permissions and driver. The interface list alone is not enough to identify a single cause.

If the interface exists but all traffic drops immediately, continue with routes and DNS. Do not hand-delete physical adapters you do not recognise; when cleaning up, only target virtual interfaces confirmed to belong to this client, and quit other proxy software first.

Step 3 — default route and multi-adapter conflicts

The Mihomo documentation states that auto-route routes system traffic into the TUN device automatically, and auto-detect-interface identifies the actual outbound interface. A laptop connected to Wi-Fi, wired Ethernet, a phone hotspot, a virtual machine, Docker and a work VPN at the same time can hit conflicts in that automatic choice.

  • Temporarily disconnect unused VPNs, VM adapters and hotspots, keeping one real uplink.
  • Disable TUN, confirm direct connectivity returns, then enable it again.
  • If only the corporate intranet, a NAS or LAN devices become unreachable, check whether those private ranges need to be excluded — do not switch all traffic to direct.
  • If the fault appears only after moving from Wi-Fi to wired, fully disable and re-enable TUN so routes are rebuilt.

Do not copy a stranger's entire TUN configuration block. Route exclusions depend on your own subnets; copying them can leak intranet traffic or permanently bypass the proxy for a target address.

Step 4 — separate "no network" from "DNS failure"

If IP addresses connect but domain names do not, or the log shows resolution timeouts, NXDOMAIN or SERVFAIL, move to DNS. Mihomo's dns-hijack sends matching DNS connections into its internal DNS module, and Windows and macOS place limits on automatically hijacking DNS requests aimed at the local network.

  • Turn off the browser's secure DNS or another standalone DoH resolver once as a comparison — not as a permanent downgrade of security settings.
  • Only on devices you administer, temporarily compare a personal DNS filter such as AdGuard, then restore it after the test. For organisation-managed security clients or antivirus network filtering, contact the administrator instead of disabling them.
  • Confirm the DNS module is enabled in the configuration and that the upstream resolvers are reachable from the current network.
  • Adjust Fake-IP, IPv6 or strict-route only when you know what they do, one item at a time, keeping the original configuration.

Step 5 — use the log to assign the fault to a layer

SymptomCheck firstNext step
The TUN switch flips backService, permissions, core startSave the verbatim error, check the official version and service state
Interface exists, everything is offlineDefault route, other VPNs, multiple adaptersKeep one uplink, rebuild TUN
IP works, domain failsDNS, DoH, Fake-IPCompare system DNS with client DNS
Browser fine, game failsUDP, rules, node capabilityCheck whether that application's connections reach the client
Only intranet or NAS unreachablePrivate routes and exclusionsConfigure against your real subnet, never a copied template

When asking for help, provide the OS version, Clash Verge Rev version, Mihomo core version, time of the fault and redacted logs. Do not publish the subscription URL, tokens, node passwords, device names or internal addresses.

How to restore networking safely

  • Disable TUN inside the client.
  • Disable the system proxy and service mode, then quit the client normally.
  • Confirm no system proxy remains, and reconnect Wi-Fi or Ethernet.
  • If connectivity still fails, record the current adapter and route state and reboot as a comparison. A reboot does not guarantee removal of the root cause, and a full network reset should not be the first move.

After recovery, rebuild the baseline from "system proxy works" and then enable TUN again — that tells you which step reintroduced the fault.

When to stop changing configuration

If the subscription is expired or the provider is doing maintenance, fix that first and retest TUN afterwards. A failing system proxy only means a usable baseline has not been established: follow the recovery steps, confirm TUN is off and any leftover routes or DNS effects are gone, then check the base network, subscription and system proxy. If the problem happens only on a corporate or campus network, network policy may be involved; do not work around organisational restrictions without authorisation. For core crashes or repeatable service install errors, search the official GitHub issues with the same version after redacting your logs.

Keep a before/after route comparison on the same device

When the system proxy mode works and TUN mode breaks connectivity immediately, the most useful artifact is the route difference on the same device, same network and same node. On Windows, route print shows the interface list plus the IPv4 and IPv6 tables; macOS and Linux have their own built-in route commands. Do not copy another device's default gateway or subnet configuration.

  • With TUN off, record the time, the active adapter, the default route and the result of one ordinary HTTPS request.
  • With TUN on, first confirm the core and virtual adapter actually started, then record the same items. If TUN was never created, a route comparison cannot prove a route conflict.
  • Compare the default route, the target intranet subnet and interface priority. Only when the route clearly changes and the failure appears at the same moment should you examine exclusion rules further; if the route is unchanged and only domains fail while IP requests succeed, go to DNS first.
  • Restore the original settings and retest the same site to confirm normal networking returned. Mask internal addresses, device names and subscription details when publishing logs.

Field meanings for the Windows command are documented by Microsoft's route reference. This comparison locates the failing layer only; it cannot by itself prove that a node stays stable over time.

Sources and update record

Material checked 2026-11-05. Primary sources: the Clash Verge Rev official quick start, the official project repository, and the Mihomo documentation for TUN configuration. All were reachable at the time of checking. The three-state table is this site's diagnostic method, not a measured benchmark.

This article was assembled with AI assistance and edited by this site against a verifiable boundary: forum cases were not rewritten into universal conclusions, and no device testing was invented.

Frequently asked questions

Why does the system proxy work but TUN break connectivity?

The system proxy only requires an application to use the local proxy port; TUN additionally depends on service permission, a virtual adapter, the default route and DNS capture. That comparison suggests nodes and core may be fine, so the investigation should move to the TUN service, routes and DNS rather than repeatedly changing subscriptions.

Does TUN in Clash Verge Rev always require administrator rights?

Implementations differ by system and version, but installing or starting a TUN service generally needs sufficient system privilege. Use the project's service mode or official procedure; do not work around permissions by disabling security software, running unknown scripts or installing unknown certificates.

TUN is off but normal networking has not come back. What do I do?

Quit the client completely, confirm the system proxy is off, then check whether the virtual adapter, default route and DNS have returned to normal. Do not run several network resets at once; change one item at a time and record the result. A reboot can serve as a comparison but does not guarantee cleanup of every network component.

Both the system proxy and TUN fail to open pages. What comes first?

Disable TUN, pin one node, confirm plain networking works, then check whether the system proxy produces a connection entry in the client. When both capture methods fail, check the subscription, nodes, core and system proxy; do not diagnose a routing fault from the mere fact that TUN was enabled.

Only some applications fail under TUN. Does that mean the virtual adapter was not created?

Not necessarily. Confirm whether the adapter exists, then check whether that application's connections reach the client and how its UDP, DNS and rules are handled. If only the corporate intranet or a NAS is unreachable, check the real private subnet and route exclusions instead of copying someone else's configuration block.

Continue reading

the service will not install · system proxy has no internet · cannot select profile: socket error · the full error-string index